Users experiencing issues with ribbon and lead qualifying

(1) Share

Report

Posted on by Community Member Microsoft Employee

Hi there,

Bit of a strange one, I have a number of users all with the same security role who - occasionally when they open a new or existing lead or opportunity - the menu for that record won't open.

Also experiencing the "loading business logic" wheel going round but not moving onto the opportunity screen when qualifying a lead.

Any ideas on both and whether these might be linked? I am assuming this will be user level access issues, but rather me spending hours going through each option, I was wondering if there was a minimum required user level access document for qualifying leads that anyone has drawn up?

Thanks

*This post is locked for comments

All responses (4)

Answers (0)

Suggested answer

Nijos 1,672 on at

Like (0)

Report

RE: Users experiencing issues with ribbon and lead qualifying

Hi,

I had same issue but got fixed after clearing the broser cache.

Please try clearning the browser cache

Check for any unsupported scripts or button rules on load of teh form

Check Business Process Flow privilleges

Nijo
Syed Ibrahim 6,257 on at

Like (0)

Report

RE: Users experiencing issues with ribbon and lead qualifying

Did you created any custom buttons on the pages using security roles permissions?
Suggested answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: Users experiencing issues with ribbon and lead qualifying

Hi Jimmy,

try the following:

1) empty browser cache

2) run on javascript browser console: localStorage.clear()

Please let me know.

If you found the answer helpful, please mark as Verified

Join my network on LinkedIn Follow me on Twitter

Thank You & Best Regards

Francesco Picchi

Microsoft Dynamics CRM Consultant, Bologna, ITALY

Independent Contractor

http://www.francescopicchi.com
Ian Judge 20 on at

Like (0)

Report

RE: Users experiencing issues with ribbon and lead qualifying

Hi Jimmy,

I had a similar issue when a case form loaded, turned out to be some unsupported JS code and Legacy forms support being turned off. IIRC, I had to remove/update some JS to fix this. Have you got some JS on your page which is checking the security role and applying some logic? I'm guessing its something in here.

Good luck!