Last Modified Date Time Attribute property

Indicates the DateTime-based attribute that contains information about when the record was last modified.

Scope

Objects: Transaction
Platforms: Smart Devices(Android, IOS)

Description

This attribute will be used as a reference for the timestamp algorithm to determine which rows must be synchronized from the server to the device. In other words, the device will synchronize those rows whose last modified date time is later than the last synchronization timestamp.

In the next synchronization, the server uses the timestamp sent by the device to compare with the value in the Last Modified Date Time Attribute. All rows modified or added after the last synchronization are considered.

Runtime/Design time

This property applies only at design-time.

Samples

Suppose we have a Chat transaction object defined as follows:

As you can see, we have set the following properties (both are required for using synchronization by timestamp).

• Logically Deleted Attribute property = ChatIsDeleted
• Last Modified Date Time Attribute property = ChatTimestamp

Also, suppose there are two friends communicating through our chat system and they already have the following rows synchronized on their devices.

Minutes later, friend1 realizes he/she has made a mistake sending a message to friend2 instead of Mom. Luckily, our chat system allows the end user to change the content of sent messages, and friend1 decides to change the text to "Hey dude! I'm at the dance club. Where r u?"

Typically, the developer implements this functionality by using the New command (not recommended) or combining Business Component Load method with Commit command in a Procedure as follows.

parm(in:&From, in:&To, &DateTime, in:&Text);

&Chat.Load(&From,&To,&DateTime)
&Chat.ChatMessage = &Text // instantiated with 'Hey dude! I'm at the dance club. Where r u?"'
&Chat.Save()
commit

The developer expects that this new row on the Chat table will reflect the change automatically on the target device after the insertion. However, when synchronization by timestamp is used, since the last message is already synchronized on the friend2 device, the updated row will never be sent (there is no hash comparison). Therefore, the appropriate mechanism for updating (or inserting) data must be implemented by the developer. In this case, the Procedure shown above should be changed for the following code.

&Chat.Load(&From,&To,&DateTime) 
&Chat.ChatMessage = &Text   // instantiated with 'Hey dude! I'm at the dance club. Where r u?"'
&Chat.ChatTimestamp = now() // Last update modified (value 10/13/17 12:06:17 AM)
&Chat.Save() 
commit

Once the row has been updated by the developer, both devices will have the following records on its offline database (convenient for friend1).

How to apply changes

To apply the corresponding changes when the property value is configured, execute a Rebuild All.

Availability

This property is available since GeneXus 15 Upgrade 8.

See Also

• Logically Deleted Attribute property
• Data Receive Granularity property