Does this also happen if you open a new page, not in a popup but full page and place the widget on that page?
Edit: You could also try to create a rest service, details are in the widget documentation. Performance will be much better too.
Note that the date is not intended to be linked to a change date of your object but this should also work. Please check the demo/sample project for usage of the date attribute property
Hi Marcel. Thanks for prompt reply and apologies for late response.
I have to admit I do not fully understand how I need to use the date changed fields from what you’ve written in the documentation. It may be I am using this wrong, but then I don’t know how to use it right I guess, but I still have the behavior where the record ID of the information I am trying to show is one record off.
Can you make the date changed variable optional instead of mandatory so we can at least get output while we’re testing/developing, when we can tolerate the high round trip behavior?
How can I best convey to you what I am doing and where the problem occurs so you can debug? Small sample project with export?
My end users like the demo project examples and they’re asking me to use the widget, but I cannot put it in like I have it now if it presents the wrong information.
Response to the date topic. What I wanted to ask is not to remove the date option, but instead of it being mandatory right now in the UI, just have it optional there so we can test without it being in place (and yes, suffer lots of roundtrips, but this does not really impact us on local desktops).
I’ll respond to the other two comments you made separately as well later.