x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 409 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Toby.Prince

User agent strings & Sage CRM

Posted By

Hello,

I was wondering if someone could explain to me how CRM decides what site is shown, based on the user agent string provided by the devices that is accessing it?

We have had a number of customers, that have updated to IE 10 (automatic update), and when accessing CRM, it sends them to the Mobile site, even though they are on IE for desktops.

The user agent string IE is using is: -

Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)

I can find this in the 'Unassigned useragents' and map it to the Desktop HTML version of CRM, but, this doesn't seem to help.

We then accessed CRM from a Nokia Lumia, with user agent string: -

Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920)

The above also always maps to the mobile site, even if specified to map to the desktop site.

Can anyone shed any light on how this works?


Thanks for your help.

  • 0

    Hi David,

    For the user agent: -

    Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)

    The device ID is NULL. I have tried setting this to '1', but it doesn't seem to make a difference. Weirdly, using Firefox as an emulator, using the above useragent takes me to the desktop site. I am very confused.

    Looking at the useragent: -

    Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920)

    This has an DeviceID of '2', the mobile site. Clearing this, it still gets taken to the Mobile site, and setting it to '1', it still goes to the mobile site. So it doesn't seem that the deviceId has a bearing on it, unless I am missing something?

    Thanks for the help.

  • 0

    Toby - what are you seeing in the adjacent deviceid column for the "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)"?

    The record in deviceid seems to control things at some level. I blanked out 9 (iphone) in our crm db because i wanted to view the standard crm site vs mobile from my phone.

  • 0

    I had to do either an IIS reset, or a straight up reboot (can't remember which) , of the webserver when i was experimenting with nulling out the deviceid. Then the change was in place.

    I wonder if you could just change the MSIE 10.0 to 9.0 in the db record, and null out the deviceid, and it would magically work. From what I have read, the third digit (10.0) in the MSIE token (before this everything was 9.0, 8.0, 7.0, etc) is most likely to be the culprit. The microsoft docs suggest that CRM is utilizing user-agent sniffing, versus feature detection, and that is the problem.

    Note - I know diddly squat about web development; I am strictly going off reading and research.

*Community Hub is the new name for Sage City