The parts were delivered on the customer order. And the sites are correct.
thank you for the response!
We have since realized that when receiving a part on a shop order locks that part. So when a user is trying to perform an action with that part number, they receive the locked for recalculation msg. For example, Part 1234 is being received on a shop order. There is a customer order with a line for that part number, 1234. When a change is made to the customer order line and saved, the user will receive the error msg.
Thank you again for the response. I have a related question, You mentioned that our users having multiple devices may be a bug. https://community.ifs.com/service-touch-apps-mwo-mro-43/allow-multiple-devices-for-touch-apps-23467 What will happen to failed transactions that are not yet addressed and out messages that have not yet synced if a new active device is created for a user?ExamplesA user has 2 devices. Device ID 1266 was originally the active device. It is now Disabled. Device ID 1267 was created and is now the Active device.The user has Out Messages for both devices.Some Out Messages were created for Device ID 1266 when it was active. Some Out Messages were created for Device ID 1267. Will the out messages for both devices sync to his mobile app? Or only the ones created from the active device, Device ID 1267? The user has Failed Transactions for both devices -- Device ID 1266 and 1267.Can the failed transactions for both devices be reprocessed? Or only the ones created for the
thank you! we will open a support case
Follow up question. Our users are being assigned multiple devices even though they always use the same device to access the mobile app. We don’t know why new devices are being created for them. Especially since the “Allow Multiple Devices” box is unchecked for all application versions. I posted a question about this previously in the community but received conflicting responses. Can you please review this community post and let me know if our user’s should be getting multiple devices? For example, the following user has 18 active devices even though she only logs in from her laptop and no other devices.
Thank you for your response. I just want to clarify.The failed transaction below is for a user with Device ID 167 and App Version 3.18. A new App Version, 3.19, is added to the Applications table before anything is done with the Failed Transaction.The App Version for the user Device ID 167 is changed to 3.19. Will we still be able to reprocess the Failed Transaction now that the App Versions are different?
Thank you for your response.To clarify that I am understanding correctly, Pending transactions that the user has that have not synced yet will be synced when the test initialization runs? And if so, are those transactions all associated with the device “dummy” ?
I’d like to filter them by whether or not someone has responded to them.
thanks
thank you for the replies
we were able to resolve. thank you!
We were able to determine the cause for the initialization not completing and the message that the Sync Process is Failing. It happens when we make a change to the user’s profile in order to display a new custom field in the mobile app. What are the steps for making a custom field visible to users in the mobile app? We are using IFS 9.
thank you, we will try that
Thank you for your help with this. We are now able to get the parts to appear in the mobile app to be received and to show in stock in the app. But the user has to initialize each time.Created and released inter-site PO for user parts. The user ran a sync in the mobile app. The background jobs were run in IFS. But the user was unable to see the parts in the app to receive until after he initialized. Parts were received in the mobile app. The parts did not show in stock in the app but did show in stock in IFS. Ran the database task “Refresh All Inventory Parts” . The user ran a sync in the mobile app. The background jobs were run in IFS. But the user was unable to see the parts in stock in the app until after he initialized.So here are my questions:Why does the mobile user have to initialize in order to view parts in the mobile app? Does the initialization process do something different than what the synchronization process does in the mobile app?
We were able to determine that the initialiation sync failing was due to a profile change.
thank you for your help!
In IFS 9, when creating a PO to order stock for a mobile user, does the Destination Warehouse field need to be populated and/or the Receive Case be “Receive into Inventory” in order for the parts to …Show in the mobile app for the user to receive Show in the user’s stock in the mobile app after receivingIt is has been sporadic that some users are able to receive their parts on the mobile app and for others the parts never show in the app to be received. And then when some receive the parts, they show in their stock in the mobile app whereas for other users, after they receive the parts, they do not show in their stock in the mobile app.
btw, we are using IFS 9
The batch sync has run but the parts in the user’s warehouse in IFS (back office) are not all showing in his stock in the mobile app. Any suggestions as to how we should troubleshoot this?
thank you for your response. What about the option to receive from Internal Order Transit? is there a way to do more than one PO line when using that receive option?
ok, thanks
Do we need to do a Force Initialization? Asking cause a know a Force one deletes transactions on the mobile app that haven’t been synced yet. thank you!
Thank you for the response. Do you know if the parts will still be available on the mobile app to be received? And if so, is there an option to receive from internal order transit? Thank you!
When the system prompts a user to reinitialize, is that also considered a Force Initialization?
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.
