Important Update: Archer Community Scheduled Maintenance on November 23–24 - New Community Launching Soon! Learn More..
2023-02-02 09:38 AM
I have a Custom Object storing data in sessionStorage. The code is very simple:
Sys.Application.add_load(function() {
console.log('Sys.Application.add_load() has been executed.');
sessionStorage.setItem('applicationId', 'a001');
});
It's very strange that sometimes this function is not executed. To be exact, with the same application, some records never trigger the function, while other records always correctly trigger it.
What is likely to be the cause of this problem?
2023-02-03 08:50 AM
Are there any other custom objects on the layout that could be causing a conflict?
Advisory Consultant
2023-02-23 08:41 AM
Sorry for the late response...I had to turn to some other tasks and leave this issue with a workaround using MOSTRECENTVALUE and a Data Feeds to trigger the notifications for comments.
When I turned back to review this issue, I found that it was just caused by simple mistake: the application has multiple layouts and I did not create the custom objects in some of the layouts!! Now I've added the custom objects to all the layouts and it's working fine.
Many apologies for wasting your time on this.
2023-02-02 10:07 AM
@Richard I've never seen that behavior before, the Sys.Application.add_load should always fire. Is the custom object inside of a tab set?
Advisory Consultant
2023-02-02 07:15 PM
Hi @DavidPetty , the custom object is not in a tab set.
Could you think of any possibility that record contents can affect Sys.Application.add_load firing? Really don't know where I should start to investigate the reason...
2023-02-03 08:50 AM
Are there any other custom objects on the layout that could be causing a conflict?
Advisory Consultant
2023-02-23 08:41 AM
Sorry for the late response...I had to turn to some other tasks and leave this issue with a workaround using MOSTRECENTVALUE and a Data Feeds to trigger the notifications for comments.
When I turned back to review this issue, I found that it was just caused by simple mistake: the application has multiple layouts and I did not create the custom objects in some of the layouts!! Now I've added the custom objects to all the layouts and it's working fine.
Many apologies for wasting your time on this.
2023-02-23 08:57 AM
No worries.
Glad you got it all ironed out
Advisory Consultant