Thank you both for your replies.
Also, Scott, thank you for reminding me I could at least add debugging code to the javascript to get some clues. However, I've spent the whole workday just trying to get the javascript to throw me some Alert messages to show what's going on.
First, the aforementioned custom button mysteriously stopped appearing on the CRM form--even after I deleted its Display condition. I couldn't get it back until I deleted and re-created the Command (in Ribbon Workbench 2016).
When I finally got that working, the javascript was mysteriously not running as expected. Long story short, after playing with the Alert messages I could generate, I discovered that apparently the two relevant javascripts (utilities.js and ribbon.Quote.js) are not loading in the correct order. The ribbon.Quote.js code is running, but it references a function in the utilities.js script, and I got it to explain that those function(s) don't exist at that point in the code, which tells me that utilities.js has not run yet.
Here's the odd thing. It looks like something is already in place that should've remedied that, but isn't. In Ribbon Workbench, the Command for this button has two Custom Javascript Actions. The first one calls utilities.js for function "isNaN". I think I see why they (the 3rd party coders) did that. There's no function "isNaN" in utilities.js, but by doing that, I believe they were trying to force utilities.js to load first, so it would be in memory when the second Javascript Action (the important one) runs. But somehow that's not working anymore....?
I apologize that this problem has taken a different direction from my original post. If I can ever get "back" to the point where I can get Javascript Alert messages AND trace my original message, I'll let you know.
By the same token, Preshma, I didn't save a copy of the trace log, and will have to get the code back to that point before I can post it as you requested.
Again, thank you both for your help.
------------------------------
Joseph Thiel
Software Engineer
Per Mar Security
Davenport IA
------------------------------
Original Message:
Sent: Mar 13, 2020 09:24 AM
From: Scott Sullivan
Subject: Request message has unresolved parameters
Have you debugged the javascript and verified the parameters are getting passed to the custom action?
------------------------------
Scott Sullivan
Protective Life Insurance Company
Birmingham AL
Original Message:
Sent: Mar 12, 2020 10:55 AM
From: Joseph Thiel
Subject: Request message has unresolved parameters
This error message has mysteriously begun to appear in our Development environment, but thankfully not elsewhere: "Request message has unresolved parameters." It happens when we click a custom button that calls an Action in our plug-ins. Nothing has changed about the custom button or action; unrelated code in the plug-in has been changed and uploaded several times. The trace log just displays the same message with a lengthy stack trace that doesn't mention anything recognizable. Logging code added inside the plugin never runs, because the plugin presumably never starts. Nothing appears in the server's Event Viewer (this is D365 on-premise). I've inspected the configuration of the ribbon button and its command (using Ribbon Workbench 2016), the Javascript it calls, and of course the C# code in the action plugin itself. There are similar plug-ins, both on our Development and Production server, which are still working; I've compared them in every way I can think of, and they all appear to be configured correctly. And my Internet search only seems to yield solutions that don't make any sense to me, at least not as worded. At this point, I am left blaming the coronavirus. Please help!
#Technical #OnPremise #D365
------------------------------
Joseph Thiel
Software Engineer
Per Mar Security
Davenport IA
------------------------------