Change scheduling assistant warning message Madrid
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2019 10:56 PM
Hi all,
I recently upgraded to Madrid. On change records, I am getting a warning at the top saying 'Scheduling conflict detected. Use the Scheduling Assistant to avoid conflicts'. I see the onload client script for this message, its called 'Notify Conflicts' but it is not active. So how is this message still popping up if it is not active? Is it coming from somewhere else? Again, this is in Madrid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2019 01:41 AM
Hi All, had to struggle with the same. manage to find that this is in UI macro as below:
here you have line 83-85 that is responsible for the same. Commented out and the message will disapear and you will stillhave the Check Conflict button . No need to remove the whole button as suggested before.
any suggestions how can we add some if condition to this message ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2019 06:53 AM
I've been struggling all week trying to find where this message was coming from outside of the Conflict change client script. After commenting out, the message is gone. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2019 09:20 AM
Hi everyone,
I tried commenting out the code in the UI Macro but that didn't work.
The code adding the warning message is located in the Conflict change Client Script.
It's an onChange client script that is also running on load (which is why it took so long to find it!). Deactivating the client script removed the message and doesn't appear to have had any negative impacts.
Hope this helps you all!
Rebecca
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2019 01:33 PM
Worked like a charm! Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2019 08:41 AM
Thanks Rebecca, deactivating the Conflict change client script worked for me.