Raiser's API does not generate "date_added" & "date_modified" instantly

1

When we create a record in Raiser, the record gets add successfully, no issue but when you try to get that records by calling API it will give all the details but without “date_added” & “date_modified”. It takes some time to generate those data, here is the link which says the same in note section.

Now the problem I’m facing because of the Raiser’s API default behavior:
When I create a record from 360Alumnu to Raiser, then it creates the record in Raiser but when I try to get that record to map “Last modified timestamp” it throws an error “No last modified timestamp found, required for Create actions” which is obvious because the record has just been created and does not contain “date_modified” but if I get that records after few mins (maybe after 15-20min) then I get “date_modified” value.

Here is the assembly: 42807a86ebbf42b38f7dec648c2c0c5a

raiser_timeStamp
raiser_timeStamp.png493×778 64.2 KB

Could you help me with this situation? Do you think we should use the “MD5 hash” for both trigger and action assembly or any other ways?

2

I’ve never seen an API do something like that. It’s just crazy behavior.

Yes, a MD5 hash will be best for this situation, where the hash excludes the timestamps and any other data elements missing when the record is created.

image
image.png752×544 27.3 KB

3

Understood! So I need to use MD5 hash for trigger and action’s subassembly both since it’s two way sync or use in action’s subassembly would be fine?

4

The system two-way sync logic uses the last modified timestamp to know when records have been updated, so trigger and actions have to use the same value.

5

Got it! I’ll do the rest of the work, Thanks.