on 10-13-2023 11:51 AM
Hello Experts,
We are getting frequent issues where the POS2JOB SYNC rule was not working properly. As a workaround, we are trying to explore for options, and in one of our consideration was to use Integration Center. Does anyone here using ODATA API to sync Position to Job Info? If yes, can you please help me how it was done?
Looking forward for your inputs/help to resolve this potential issue raised by business.
Thank you
Sid
Thanks, Jasper. Let me check further on this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Technically you could just navigate from EmpJob to the position and retrieve values from it. Make sure it's a scheduled integration from SF to SF via odata to achieve that (assuming it's volumes up to 1000). The main thing to perhaps hard code is the effective date (as you'll want a different one likely), the sequence can/should be empty and you'll need a sensible event reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello nathanwilkinson,
Thank you for swift response! Kindly note that we are facing issues when we perform transaction for future / past date propagation.
For Ex:
There were few incidents raised as well,
878136 / 2023, 893504 / 2023, 893528 / 2023, 893642 / 2023, 893625 / 2023.
Appreciate, if you have any suggestion for me.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you first explain what your issues are and when they occur.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
9 | |
6 | |
6 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.