One of our clients was experiencing some trouble with the Dynamics 365 flow button for “Accounts”. When they clicked the button, its dropdown menu opened but got stuck on “Loading…”.
When checking the console in the Developer Tools (F12), there was an error popping up that said:
error on line 1 at column 1106: attributes construct error
After a little online research, there was nothing concrete to find about this problem. So the only thing there is to do, is dive a little deeper in the error message ourselves.
It looks like the menu dropdown gets loaded as XML which then gets parsed into HTML elements. This error gives us a clue that there must be something wrong with the given XML… But what?
Because the flow button was working fine with other entities, the problem must have something to do with workflows registered on the Account entity. And more in particular, the workflows registered “As an on-demand process” because they get loaded into the dropdown menu.
Next, we deactivated every workflow registered on Account at a time. This way we could check whether the dropdown was loading or not. There was indeed one workflow that was causing this error and thus stopping the dropdown from loading.
As you can see in the Process Name, a part is surrounded by double quotes. This scrambles the XML, making it invalid and setting off the error.
Just by replacing these double quotes with single quotes, we were able to fix the problem. The flow menu dropdown now loads and shows the workflows registered as an on-demand process like it should.
So there we have it. Just be careful in naming your workflows and/or other attributes. It could save you a lot of time trying to find out why something stops working or sets off an error!
THanks for this post, And i realised , You can add one more point here, like don't use special character, ex:!,@,#,$,%,^,&,*,"
late to the party but what should i look if the flow button keeps stuck on loading for all entities but for some users only? i've already checked roles and user licenses.any ideas?
Hi Ioannis. As you state it's for all entities but for some users only, it does seem like it's a privilege issue. I would check if the users where the button does load, have an extra role assigned compared to those where the button does not load. Also, if possible, I would try and see if the Developer Tools (F12) can make you a bit wiser about what is going on there. Just open it up and then click the Flow button. The error should be printed in the Console.
[…] bericht Dynamics 365 flow button keeps loading verscheen eerst op […]