Skip to main content

We are using customized mobile profiles more and more. As of now we use the same profile for SAs in different countries (profiles). Are there any issues we should be aware of when it comes to using custom fields from Alliance in Mobile Customizer? We have situations where the same field is added in to all profiles, but the data is different (eg. a field named Filter 1 on Installed Item), and this will have different data in the different ptrofiles, but it seems in Astea Mobile that the data shown does not belong to the right profile: we may have Filter 1 values “Big filter”, “Medium filter”, “Small filter”  in one profile, but only value “Medium filter” in another. Still all 3 values are shown as an option on Astea mobile for an Installed Item belonging to the latter profile. We need to be sure that we don’t get any data cross-contamination.

Would it be adviceable to use a Mobile Custom profile per Astea profile?

Hi Bjørn,

I think you should use one per profile but perhaps Reid or someone has other thoughts.  This way you can ensure you have the correct customizations.  However, remember, you need to adapt the URL for each customization profile too.

 


Reply