Skip to main content
Solved

Mobile place_ext issue

  • April 20, 2021
  • 3 replies
  • 84 views

Forum|alt.badge.img+9

Hi Team,

We have a requirement to create PLACE_EXT for handling additional properties, but unable to download & work with the values in Mobile.

Can you please point to any documentation or examples to implement the same. Ex :- Sync Rules, Screen Client Scripts for Reading & Updating values for Mobile Thanks in Advance

Best answer by MatAntoiF

Hi

Ok, I managed to get it working. All scripts and screens and sync rules need to point to the parent table in this case the place table. I had another screen on the mobile that still called the place extension table and it influenced the new screen I created even though that screen was inactive. I also deleted the place_ext sync rule and only listed the place_ext fields in the place sync rule but called them from place not place_ext (e.g. <attr>PLACE.METRO_RURAL</attr>) I did not call place_ext table in any sync rule or client script either.

This topic has been closed for replies.

3 replies

JOOLSE
Hero (Employee)
Forum|alt.badge.img+11
  • Hero (Employee)
  • April 20, 2021

Is this the FSM app or the MWO app?


Forum|alt.badge.img+9
  • Author
  • Hero (Partner)
  • April 22, 2021

FSM


Forum|alt.badge.img+9
  • Author
  • Hero (Partner)
  • Answer
  • May 17, 2021

Hi

Ok, I managed to get it working. All scripts and screens and sync rules need to point to the parent table in this case the place table. I had another screen on the mobile that still called the place extension table and it influenced the new screen I created even though that screen was inactive. I also deleted the place_ext sync rule and only listed the place_ext fields in the place sync rule but called them from place not place_ext (e.g. <attr>PLACE.METRO_RURAL</attr>) I did not call place_ext table in any sync rule or client script either.