Mac Versus PC - Different Browsers - What works and what doesn't on Anaplan?
I just wanted to create a post to allow users / model builders to share their experiences on the differences / issues they face when viewing a model / dashboard on a PC vs MAC and different browsers:
It would be great if we could all share and then we can produce a list together of the known differences!
So i'll start by sharing what issues I've been facing:
Emojis and Special Characters - I always use google chrome on a PC so I haven't seen any issues with emojis and special characters on a PC on Chrome, however many MAC users experience broken Emojis and Special Characters for example a simple arrow emoji will display on a PC on chrome but not on a MAC. Does anyone have a list of emojis / special characters that work on both MACs and PCs?
Images - I have found that on some occasions images will display on a PC on Chrome but not a on MAC. I have tested using various image hosting sites and have found that some sites will dispay on both PC and MAC - Imgur.com. However this would only be suitable for public images.
It would be great to hear from the community about your experiences!
Agree this is a really useful topic. On the specific point about emojis/special characters I dimly recall some discussion a while about the UX supporting specific character sets, or at least having been tested and proven to work with specific sets. If that's true then two things would be great for us to know:
- what are the proven encoding types/sets?
- and maybe even more importantly does this still hold true in the new UX? Or are there more/fewer limitations? It'd be useful to add to the topic any differences that then apply between classic and new UX across PC vs Mac, between different browsers etc.
Great topic @usman.zia and now with the new UX and being able to view pages on mobile this will be really important.
I agree with @CallumW with regard to special characters this definitely deserves a best practice mention, particularly in the Planual. Regarding images, i think some type of best-practice around naming conventions would be good too, especially if you use a lot of them.
I also use Chrome on an iMac and a PC and never had any problems with images. You actually introduced me to imgur.com but because of their retention rules, I chose not to use it. Instead, I worked with the e-commerce teams at my client to get a unsecured directory made where I can host the images.
Images are really important with the clients I work with, especially retailers where I need to show the product images, so the responsiveness of the dashboard or the page needs to be perfect. So far it has been. We all know the enhancements that would make dashboarding better though - the ones on the idea exchange. Symmetry on the dashboard makes it look more professional. I can't tell you how much time I spend adjusting the width of text box with a mouse.
I have to admit though, I don't use special characters - just a personal preference. I feel they clutter up the screen.
And I've never tried animated .gif files. Would be interested to hear from others if this has caused anyone issues. I would love to use them as a "help screen" on a dashboard.
@rob_marshall - that's a helpful reminder, thanks. But it would still be useful to understand a little more precisely what the constraints are here. For example, is the issue really to do with Anaplan itself, or just to do with different browsers supporting or not supporting particular characters sets? Or even if it's something that can vary depending on how the specific browser has been setup for that particular user (am thinking about language/locale settings, for example)?
So let's say an emoji or special character input by one user might render correctly, and is then converted to a background code in the Anaplan platform (presumably). If it then won't render on another user's browser is that because the destination browser can't unencode it properly, or does something get lost en route through the platform?
Looking at this more widely it's not just limited to use of emojis (which is really a matter of personal taste anyway) - the same considerations are likely to apply when using accented characters from non-English languages or non-Roman scripts, which of course could be massively problematic for (say) multi-territory deployments.
I believe it has everything to do with how the different browsers interpret the emoji's as they are not uniform. I know we all like to use them to make the dashboards look better, but they could very be harmful to the model. Best case is to not use them, but really not use them within modules on or in line items.