Discussion Forums

Mistake in my implementation using the API or bug?

 
New Member
3 posts

Hey,

I’m using the API to create new records of contacts and companies. When running my script (typically post from a form) the record is written to solve360, but when trying to see the record with a different account than the api-token user (used in the script) I don’t see the new record on top of ‘all contacts’ sorted on the ‘last update’ field. However, when I search for the record it is found with min since last update. Also if I filter on ‘Shared’ and the ownership of the record it is show correctly. Hope my explanation was somewhat clear.

It’s just a small thing, but a bit annoying when developing against the system. Is there anything I can do different in my code to prevent this behavior?

- Snorre

Avatar
Administrator
3952 posts

I think I know what may be happening.  Solve caches search results for some filter options including the “All ...“ option by user and updates the cache as data changes.  Most likely in this specific case the filtered lists cache is being updated only for the user account that created the item and not the others.  I’ll have an engineer dig into this for us.

You can spoil/update the cache for any other user by updating a page e.g. Add the item, switch to the different account, simply star an item, click refresh list.

Avatar
Administrator
3952 posts

I think we’ve nipped this one.  When you get a chance can you run another test…