In some synchronizations, the time that a remote entity was last changed is saved into a Drupal field or field property. In some cases that time is provided in an unsupported format e.g. wrapped in an array etc. We can support such cases by allowing to fetch the time from a computed value instead of directly getting it from a remote entity property. Computed values provide extensive abilities in transforming any property from the remote entity in practicality any way required.

Comments

krystalcode created an issue. See original summary.

  • krystalcode committed a028f3d1 on 4.x
    Issue #3567411 Added supported for computed remote changed values
    
    By:...

  • krystalcode committed a028f3d1 on 5.x
    Issue #3567411 Added supported for computed remote changed values
    
    By:...
krystalcode’s picture

Status: Active » Fixed

A follow up will be required for supporting this when saving the remote changed time after an entity export for preventing import/export loops.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.