Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Ribbons Freezing with sitemap customizations RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have done a few Sitemap customizations with sitemap entries pointing to a new website on the same server, nicely integrating with CRM.

    However having those links somehow freezes the ribbon every now and then. You click on the sitemap and the Ribbon stops completely, no mouse over effects anymore, no clicking on items. When you change the Sitemap nodes a few times (not necessarily to CRM items, but also between the custom links) it starts working again and keeps workig until you navigate to a page reloading the sitemap and then the behaviour starts all over.

    Perfectly reproduceable and perfectly annoying :)

     [Update] The Ribbon freezes with the last selected ribbon of CRM. I would guess CRM is looking for information on the loaded page to determine which ribbon to load and just stops instead of using the default ribbon for the entity. This is only happening on ribbons within opened Entities, e.g opening an Account or Contact.

    Monday, March 7, 2011 7:47 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello -

    It seems like there is more than one issue here.  Are there two problems? Ribbon freezing and that the links are opening the incorrect page? 

    By talking with support they will log the bug accordingly.

    • Proposed as answer by Jim Glass Jr Thursday, March 10, 2011 5:31 PM
    • Marked as answer by Jim Glass Jr Tuesday, June 7, 2011 8:41 PM
    Thursday, March 10, 2011 5:21 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I suggest opening a support case with Microsoft so that we can prioritize the bug to fix it in the future.

    • Marked as answer by Jim Glass Jr Tuesday, June 7, 2011 8:41 PM
    Friday, June 3, 2011 11:27 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello -

    Are you navigating through the web app or the Outlook client?  Can you collect the server traces when this occurs?

    Thanks,

    Brandon

    Monday, March 7, 2011 8:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Runnning from the webclient. Ill see for the traces and post them asap.

    [Update] No errors in the trace. Verbose is somewhat unreadable for me, without a clue what im loooking for :)

    [Update2] This is also happening when you create a link via the customize. Customize the Account form, add a navigation link to any URL, save and publish. Open an account and click on the nav item => ribbon freezes.

    [Last Update] This seems to be a bug in CRM. Created a new organization, Customized the account form by adding a link in the navbar to a webpage. Save & publish. Open an account record, select the new navbar item. Ribbon is dead.

    Tuesday, March 8, 2011 7:09 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello -

    This seems like a product issue.  Feel free to contact support.  To workaround this issue you can click on any of the main form sections or entity tab to enable the ribbon once again.

    Thanks,

    Brandon

    Tuesday, March 8, 2011 10:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    How do actually report a bug? Clicking on any item actually loads a different page, which is not desireable.

    Wednesday, March 9, 2011 2:06 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello -

    It seems like there is more than one issue here.  Are there two problems? Ribbon freezing and that the links are opening the incorrect page? 

    By talking with support they will log the bug accordingly.

    • Proposed as answer by Jim Glass Jr Thursday, March 10, 2011 5:31 PM
    • Marked as answer by Jim Glass Jr Tuesday, June 7, 2011 8:41 PM
    Thursday, March 10, 2011 5:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No, just the freezing issue, but your workaround would navigate away from the page you want to see and thats not desireable :)

    So to actually file a bug you would need to open a support case with Microsoft?

     

    Friday, March 11, 2011 7:28 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I suggest opening a support case with Microsoft so that we can prioritize the bug to fix it in the future.

    • Marked as answer by Jim Glass Jr Tuesday, June 7, 2011 8:41 PM
    Friday, June 3, 2011 11:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We do have exactly the same problem. How did you fix this?

    Kind regards,

    Alexander

    Wednesday, March 26, 2014 8:26 AM