Connector Improvement: Workday Connector - Creating a composite primary key
Answered
I needed some help with the Workday connector . I have put together an aggregated report in Workday which we plan to upload to Snowflake. I need to use a combination of 5 columns to produce a composite primary key but since few of them contain null records, Fivetran does not accept them. The report fails to load accurately due to this issue. Since this is an aggregated report, we cannot make any changes to the Workday report to include any unique identifier. Ideally, we believe the connector should be able to identify that each record is unique and may create its own primary key for MAR tracking purposes. We would really appreciate it if someone could help us in solving this problem.
-
Hi Parthiva -
Currently we don't accept fields that could contain NULL values as a candidate for a Primary Key. We will take this request into consideration, but it's not currently planned at this time.
Is the data in the report something that you could pull from the Workday HCM connector we support?
Thanks,
Erin
-
Hi Erin,
No, this is financial data, so the Workday HCM connector might not work. I have raised a ticket here for this.
Thanks,
Parthiva
-
HI Parthiva -
That's good to know! We are currently testing our Workday Financials connector in Private Preview, so we can definitely get you set up with that connector if that would be something you are interested in.
Best,
Erin
Please sign in to leave a comment.
Comments
3 comments