and more in a single search tool across platforms. Read the announcement here. |
03/11/2024 01:40 PM - edited 03/13/2024 03:20 PM
we are trying to pull the user from Workday which was recently converted from Contractor to employee. during the conversion, contractor record was terminated and employee record is generated. When we run a single user import putting a filter to import employee, user is successfully converted but when we are running the full import without any filter, import is unable to pull employee record and user is not getting converted.
Please advice or suggestion if anyone faced this issue earlier
Thanks in advance
03/11/2024 07:41 PM
Can you share filter used.
03/12/2024 11:44 AM
Here is the filter :
03/12/2024 03:06 AM
Hi @abanduni , you can ask Workday team to share a integration field like
"CUSTOMPROPERTY12": "Worker_Data.Integration_Field_Override_Data(Field_Reference->ID=='EEtoCCW').Value"
Based on this you can make a decision in inline preprocessor - "DELETE FROM NEWUSERDATA where customproperty12='Y'",
You can customize it based on your need.
Thanks,
Amit
If this answers your query, Please ACCEPT SOLUTION and give KUDOS.
03/13/2024 06:07 PM
we are unable to pull employees record from Workday. Where to put these field employee or contractor record?
thanks
03/13/2024 07:42 PM
Does it works from SOAP UI/Postman
03/14/2024 08:01 AM
Using single import it pulls the record but when we are running without filter it is not pulling the record in postman.
03/14/2024 08:12 PM
You need to fix postman issue first
03/19/2024 07:21 PM
You need to fix issue in postman first
03/12/2024 11:43 AM
typo in the last line "import is unable to pull employee record and user NOT getting converted."
03/12/2024 02:20 PM
Hi @abanduni as an FYI you can always edit your own post by clicking the green "V" followed by "Edit Message" or "Edit Reply"
03/14/2024 08:32 AM - edited 03/14/2024 08:33 AM
Hi @abanduni , full import might also be bringing up the record it might be that it is over written by the contingent worker record or vice versa.
In the filter above instead of employee_ID if you use Contingent_Worker_ID , you might find another record for same person.
If that is the case you need to find a way to discard the record that you dont need. For which please refer my response above , you could either have a flag as I said above or use status flag to determine terminated or converted record.
SOAP / Worker API will send both profiles , you need to eliminate one that is old and not needed. There could be multiple ways doing that.
03/14/2024 11:25 AM
Hi Amit,
In the logs i have seen that employee is not been pulled at all from workday. Can you check if i need to update anything in the request filter to pull both records. Once both record are pulled we should be able to use preprocessor like you mentioned above.
03/19/2024 01:20 AM
Hello @abanduni,
Can you please share your "USER_IMPORT_PAYLOAD" and Total employee on the page size.
What is the PAGE_SIZE mentioned in the connections params.
Thanks.
03/19/2024 04:58 PM - edited 03/19/2024 04:59 PM
03/19/2024 08:35 PM
Hello @abanduni,
May i know why you have mentioned the below tag, if you mentioned the below tag, it will only work in the incremental case, Once you remove it then it will only considered as the Full Import.
---------------------------------------------
<bsvc:Transaction_Log_Criteria_Data>
<bsvc:Transaction_Date_Range_Data>
<bsvc:Updated_From>${USERS_LAST_IMPORT_TIME}</bsvc:Updated_From>
<!--Incremental import **start date from which changes should be tracked** :-->
<bsvc:Updated_Through>${CURRENT_IMPORT_TIMESTAMP}</bsvc:Updated_Through>
<!--Incremental import **end date till when changes should be tracked** :-->
</bsvc:Transaction_Date_Range_Data>
</bsvc:Transaction_Log_Criteria_Data>
-------------------------------------------------
Please validate it in the SOAP UI.
Thanks.
03/21/2024 02:12 PM
Yes it should work in incremental order. When we are converting from employee to Contractor, it is working fine but for contractor to employee it is just terminating the contractor and not switching to employee.
Thanks
03/27/2024 07:54 PM - edited 03/27/2024 07:54 PM
@sudeshjaiswal any advice on this?
Thanks
03/27/2024 07:56 PM
Did you validated in SOAP UI ?
03/28/2024 11:22 AM
Yes, it is showing in SOAP UI.
04/01/2024 06:20 PM - edited 04/01/2024 06:21 PM
how does both effective_from and updated_from in one payload?
is updated_from picked up when incremental import runs or both(effective_from and updated_from) are picked?
If i need to pick any data from workday with incremental import based on effective date will effective_from work in the workload?
For example, Future effective title change should be imported on effective date.
04/16/2024 11:51 PM
Hello @abanduni,
Only updated_from is picked up when incremental import runs.
the system typically looks at the "updated_from" field to determine which records have been updated since the last import. This means that if a record's "updated_from" date is later than the last import, it will be included in the incremental import
Question : If i need to pick any data from workday with incremental import based on effective date will effective_from work in the workload?
Answer : No, Only updated_form will work.
Thanks