Hi @wickrambug, You would first need to look at the data to determine why it is so large e.g. are there errors blocking the sync, is the build up on the device on in the mm_message_out queue on the server, are there a large number of entries for the same table? From what I have seen it is usually either that a large update has been done to a table that has flooded the queue and needs time to clear down or an inefficiency in the sync rules where the rule could be further filtered or fields excluded or could be set to run less frequently. It could also be that the mobile user is not keeping their device active for long enough for the message to be sent through. Kind regards, Lee Pinchbeck Crystal. Thank you for the clarifications @Lee Pinchbeck
Hi @wickrambug, The fields should be populated when the mobile device syncs back a confirmation of receiving the sent Task, it is part of that confirmation sync message. If this is not occurring consistently this may be due to signal issues on the mobile or a large sync queue that the system needs to clear. Before you can set the app param you need to make sure the Business Rule to create the event entry based off of these fields being set is correctly set up. You can choose any value for the event type from the created event types in the code table event_type. If a suitable one does not exist you can first create it in the code table. It will then appear for selection in the Business Rule. Once the Business Rule is set the app param then needs to be set to have the same event type as the Business Rule. Hope this helps, Lee Pinchbeck Hi @Lee Pinchbeck,Thank you for your answer.You mentioned, “a large sync queue that the system needs to clear”. Is there a way to overcome this scenario
Hi, You need to allow multiple endpoints for the application. You can do it for all users by changing the MetrixEndpoints.xml file at C:\inetpub\wwwroot\FSMServerXXXXXXX\Client If it is select users it would be more complicated I believe. Hi Lee, It means we can have multiple endpoints within the <endpoint> tag right? <MetrixEndpoints> <endpoint name="FSM6U2DEV" address="net.tcp://BAWILK0:808/FSM6U2DEV/M5Service.svc" binding="customBinding" bindingConfiguration="CompressedNetTcpBinding_IM5Service" contract="Metrix.UI.Communication.IM5Service" /> <endpoint name="FSM6U2TEST" address="net.tcp://BAWILK0:808/FSM6U2TEST/M5Service.svc" binding="customBinding" bindingConfiguration="CompressedNetTcpBinding_IM5Service" contract="Metrix.UI.Communication.IM5Service" /> </MetrixEndpoints> like this, please correct me if I am wrong.
[quote=Lee Pinchbeck]My understanding is that Refresh Cache refreshes only the files relevant to the changes made and leaves other caches. Refresh Cache (Full) refreshes the full cache. This is set to be removed at some later version. Both of those push to refresh all users cache not just the one that initiates it. Refresh integration just refreshes the caches related to any integrations in place. Hope that helps.[/quote] Crystal and thank you for your explanation [user=299]Lee Pinchbeck[/user] :thumbsup_tone2:
Already have an account? Login
No account yet? Create an account
Enter your 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.