When/how is CASE.Remote ID Hash property set... as they are blank

I have recently added a new host, but it appears that any test cases created don’t have the CASE.Remote ID Hash set.

Can someone explain when/how this property is set?

Its working on existing hosts, as shown below.

Screenshot shows CASE SUMMARY DATA.Case Remote ID Hash property is blank for our new Internal host cases - this data is synced from Internal host → Central.

Thanks
JonathanFS

Could be a version mismatch maybe. What version is the new host which you have created?

Hash IDs were only added in 24.2, so if it is older than that it won’t have them to sync.

All hosts are running 2024.2
New Internal host

Central

We recently upgraded to 2024.2 and this is the first new host I have created since that update occurred.

Shouldn’t this field be automatically created as it’s a Data Object Attribute

Thanks

Yes, if they are both on 24.2+ then it should be automatically synced across.

Can you just confirm on the Internal app if those same records have values for their “ID Hash” Attribute. That will narrow down if the issue is on the source app or in the syncing process.

Thanks Bob

You have solved this issue for me, when I look at Tasks on the new Internal host I can see the ID Hash field has values and the Remote ID Hash is blank, this is the field that is wrongly being used in the sync routine…

The API Call Create or Update Summary Case on the Internal host is using the wrong property in the Tasks table.

I have updated the API Call and now the Remote ID Hash is being populated in Central and 24.2 links are working as expected.

Really appreciate your help in fixing this.
JonathanFS

Ah ok, I actually thought you were using Remote Object syncing, in which case the remote ID/hashes should be automatically populated, I didn’t realise you were using API syncing. Glad you have sorted it!

1 Like