Hi,MWS is taking more time to process the PUSH sync task. This delay could be caused by one or multiple entities experiencing slow execution.To identify currently executing slow SQL, you'll need to check the active sessions in Oracle, which requires DBA support.If you can consistently replicate this issue for a user, then gather the Sync traces (ensure it's enabled before testing) to pinpoint the slow SQL queries. This problem is likely associated with a large dataset or poor SQL execution within the application entity.Sometimes, a single Sync Task may receive a large number of records simultaneously for synchronization. Check the Push Queue and observe the data change pattern. Do you notice a significant increase in the number of push queue records within a short interval?
Hi,This could be a defect or incompatibility were server API has changed since mobile app logic is developed. Best to check with support team to see any fixes.
This is because of missing projection grants. Mobile security Groups grant the permission for the background data sync. But to perform online actions/queries, you also need the relevant projection grants.
If the Entity model has no overrides for objversion format then cloud resource should have the same (Means no ‘ObjversionFormat’ setting). If entity model has the code gen property to override the objversion format (to number) then your cloud resource should specify the same (ObjversionFormat = "number").Hope this will help to fix your application cloud resources. if you have any further queries pleas post here and will try to answer.
Hi Default format of OBJVERSION is ‘timestamp’. You only set it as number in the cloud resources to override the default. As per your generated event, I assume cloud resource has ObjversionFormat = "number" which is the root cause for the issue. Do you have access to the c# code? it looks like this entity is not part of the CORE release and could be added by a customization. So please check with the team who did the modification.Hope this helps.
Hi,What’s the Entity Name behind this faulty event? And also pls share the error. Fnd Event Action SQL is auto generated based on the format of the OBJVERSION attribute in the Entity Meta data in the IFS database model. Mobile only supports timestamp and number. if you do not see the single quotes means the entity has number type OBJVERSION. You will see single quotes for time timestamp type OBJVERSION. This could be an issue with the cloud DLL where it has incompatible meta data. To confirm that pls share the additional details with us.
Hi,You can deactivate this ‘Mobile App Daily Statistics’ scheduled Task from the Solution Manager. it will only effect mobile App’s lobby pages. Basically it will stop collecting daily statistics on active applications. As you have deactivate all mobile apps, it’s safer to disable this Background Task as well.
HiGood that you have resolve the error which is not directly related but that might be good idea to clear them to narrow down the issue. Could you please give me below details?Entity name your files exist (which are not syncing) Field Definition of missing data (i.e. SQL value/Expression)
Further, you can read about troubleshoot data Synchronization in below article: https://docs.ifs.com/techdocs/23r1/030_administration/040_native_apps/095_troubleshooting/30_troubleshooting_synchronization/
Data Sync API is not public and it’s in the Java Middle tier and not customizable. But what you need is to find the root cause for the error you see. To do that, you need additional traces. You can get them by enable sync traces for your app/device (Via the edit settings, enable trace for Server). Then it generate a trace file which has more details about the error you se in the Sync Task.
Hi,There are some unclear areas in the modification. For example. you do not need the ‘fetch’ as far as I can see because the Long Description is already part of the entity.However as your update to the JT_Task originates from a integration, this should work. i.e. as soon as JT Task get updated, mobile should create a Push Queue record in the back end and then it should be executed and resolve the owners of the JT Tasks. Do you see push queue records after perform Jt_Task_API.Modify()?
HiMobile data sync has some restrictions. Need to understand your flow in detail to see whether you hit any know scenarios.Any changes done in the server from a mobile transactions does not sync to the same user device the transaction has originated. if you have PLSQL expressions to fetch data from a different table other than your target table, then data sync does not aware about that change.
HiWhat type of fields are they. Do you have a SQL expressions in the implementation? Does this filed get updated in the back office or in the mobile?
Example in the CORE. ServiceEngApp query MobileUserAssortInvPart { syncpolicy Batch { syncschedule = daily at 00:00; } }
Hi Sync policy ‘None’ indicates this as a local query which runs on the local database (offline). To sync data from backend, you should use relevant sync policies for example Batch/Push. You should see a sync rule associated with your query in the ‘Sync Rules’ tables in the solution manager.
Hi,offlinequery had been deprecated from Projection and moved to the app model instead. This has been done when mobile started to support split projections. So from 23.1 EA onward you should move the offlinequery to the app model as end of support for this deprecation.
Hi,We recently done a improvement (App10 UPD22) to minimize the chance to get the deadlock. But deadlock can still visible if the application does lot if frequent changes to Push type entities. So please review the Push Queue to identify such frequent changes. What’s the 2nd SQL which blocks this DL condition?
Hi,IFS Cloud Mobile use the same basic data defined in the EDM file types. So you could check what file types are allowed in the back end. We sync this information to device and use when ever user choosing files to upload.
Hi,You will need to reactivate the device to apply the newly assigned Context.
Hi, Yes growing out queue will impact the data synchronization. It’s not the only reason but there are many. But in your case it’s good to address that first. 700k out queue messages can indicate that you have lot of installed app devices which are still active but no longer downloads data because of device might be physically offline. Which means back end data sync process keep filling out queue continuously . So you need to clean-up them. In the latest version we have a new functionality call ‘Inactive App Device’ which has been implemented to prevented this by automatically clear such out messages and other related data if a device has offline for a longer period. But for UPD9 you might need to do this manually. One way is check the last active time of the device from the Install device App and identify the user/Devices which are offline for a longer period and clean their data manually.
15 min Batch shedule recommended as the entity can have high data change frequency. Yes you cannot change the default filter without a modification.
Hi,If you can modify the app:One of the way is to set the Customer Entity as push enabled entity. So when ever a customer get created in the back end will push that to the device. Other option is to use ‘On Demand Sync’ capability on the Batch entity where you user can download additional data on demand. So you can download newly created Customers from the back office which are not yet sync to the device. So still you can keep ‘Customer’ as a batch entity + adding support on ‘on demand download’. But all above need a modification to the app.Via configurationIf you need to achieve this just from configuration, then keep batch data frequency is to 15 (Which is the lowest) is the safe option. ‘On Change’ is not suitable for fast moving data like customer. It’s is more suitable for entities like ‘Country Code’ which has very low change frequency. Putting On Change to a fast moving entity can cause performance issues. Hope this helps!
HiNo one has reported any bugs around this in 23 track as far as we are aware. So most probably it could be a issue like wrong configuration in the PS filter.
Hi,When you add the PS filter you can view all available attributes in the next tab “By Entity”. So should only use supported attributes to build up your filter condition.
What’s the IFS cloud version and SU level?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
