Hi Bjørn, 
Is it working in your UAT environment (just not in PROD?)

If that’s the case then you can try exporting the Mobile Customization from your UAT environment and  then importing that into PROD, see if that solves the issue (make a backup of your existing customizations beforehand so you can revert back if need be).

If it’s not working in your UAT environment either, then what if you add a custom varchar field to the same screen on Alliance and Mobile temporarily...if you populate that varchar field with data on the Alliance side and send a re-dispatch out to mobile does that field display the data properly?  That should rule out whether it’s a data flow issue or a screen rendering issue with this particular control...so if that displays properly then try removing the drop-down control on mobile for one of your existing custom fields (and have it just display the ID value instead of using the drop-down control to show the description) and run another test. If the screen on mobile shows the ID properly in this case then it’s most likely an issue with the mapping that is done via the drop-down lookup.  If you don’t see anything obvious in that then I think you’ll need to log a support case for it in ServiceNow.
Thanks,
Reid

Hi Reid - we have the same issues in UAT.

Could it be an issue that we have 4 profiles, and if the custom fields have the same name/id in each profile? 

I’ll test a few things, and log a ticket if it can figure it out

Hi Bjørn, 
Have you re-published the customization in the Mobile Customizer application for each of the 4 profiles?  If that looks good then check the mobile log files on the server, see if there are any error entries captured in those when it tries to download the service order (maybe it’s missing a DIFFERENT cst_ field when it does the download and therefore ALL custom fields are failing as a result or something along those lines...).
Thanks,
Reid