We are experiencing difficulties with the our IFS FSM application when updating or initializing new designs and features across devices. A sync rule has been created and applied to ensure that all devices reflect the newly designed templates and product updates. However, devices are not displaying the updated content correctly, and critical elements from the templates are missing.
Detailed Description:
Sync Rule Application:
A sync rule was configured and applied globally to update all devices with the latest changes in task templates, product attributes, and other new design features.
Problem:
Despite applying the sync rule, devices are not showing the updated task templates or product attributes.
Certain critical elements from the updated templates are missing on some devices, preventing users from accessing the new designs and features as expected.
Troubleshooting Steps Taken:
Cleared app cache and app data on affected devices.
Reinstalled the IFS FSM mobile app on device.
Re-initialized the application on the devices
Current Status:
The issue persists despite the above efforts, with devices still not reflecting the updated content.
Any idea how to solve it ?
Design Changes and Table Updates Not Reflecting After Initialization in IFS FSM
+3
+5Hi
Initially, check the output of the sync rule manually. You can run the initial query or a related query in XML Poster to verify if the expected values are retrieved correctly.
If specific users are affected, please review the sync rule conditions and ensure they align with the affected users.
+3Could you clarify if the reinitialization process from the admin screen should trigger all sync rules to run based on the initial query?
+5Yes, all the active sync rules are triggered when the user initializes the device from the Admin screen on mobile.
You definitely want to run the initial query of the sync rule in XML poster to verify it returns the data you are expecting. If the results contain the data, verify the data is in the mobile database after initialization. If the data is in the mobile database, then there is something wrong in your screen designs.
+3I check the person sync rule. The result is correct.
For some reason it is initializing with empty database:
Another thing ... the last run is always empty.
I haven’t worked with FSM for a couple years, so I’m straining my brain a bit here. If you don’t have the user’s person record in the mobile database, there is something fundamentally wrong with the configuration. First thing I notice is Delivery Method of the PERSON sync rule. I can’t imagine why that would be Real Time. Check the FSM Sync Rules, but I believe that probably should be one of the Batch methods. For Real Time sync rules, the Last Run should be blank. That only populates for the Batch rules that update data through mobile replications. It’s been awhile, so I may be off. Hope this helps.
+5I check the person sync rule. The result is correct.
For some reason it is initializing with empty database:
Another thing ... the last run is always empty.
Hi,
After updating the person's data, please check if the record appears in the mm_message_out table.
Before syncing the data to the mobile device, the record should appear in the mm_message_out table.
You can run the following query to verify this:
SELECT * FROM mm_message_out WHERE device_sequence = xxx;
If the record does not appear in the table, please check the person extract rule in the Extract screen and verify whether it is active.
+3Let's check.
Updating the field:
Checking mm_message_out:
After the update, the Person table is not supposed to send anything to the device.
---------------------------------
Yesterday I updated the user role:
Anything from the user setup I need to check ? regarding the role for example?
Database structure was received but withou data.
+3I check the person sync rule. The result is correct.
For some reason it is initializing with empty database:
Another thing ... the last run is always empty.
Hi,
After updating the person's data, please check if the record appears in the mm_message_out table.
Before syncing the data to the mobile device, the record should appear in the mm_message_out table.
You can run the following query to verify this:
SELECT * FROM mm_message_out WHERE device_sequence = xxx;
If the record does not appear in the table, please check the person extract rule in the Extract screen and verify whether it is active.
Could you please help me? How can I test it? Using XML Poster. What should I change in the code below?
Hi
There are a lot of different issues being discussed in this thread. Regarding the original post, you wrote “devices are not showing the updated task templates or product attributes.”
The output from your mm_message_out query explains at least part of the problem with product attributes. The Exception shown in the metrix_response indicates that you have a sync rule for attribute_value_lkup_view, and that the sync rule is improperly configured with a Delivery Method of Batch - Delta. You cannot use Batch - Delta sync for database views because there is no modified_dttm time to determine which records to send. Changing the sync rule to Batch - All will resolve that part of the problem.
It looks to me that there are other configuration issues in your environment. You may want to consider a configuration audit from an FSM Mobile expert.
+3I will consider your suggestion for the configuration Audit, thank you.
Alson thank you for the advise of the sync rule, it solved part of the problem! Thank you!
+3Thank you all !
The issue is related to some hardcoding on the screen, and the synchronization problem is still being evaluated.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.