Forum Discussion
TypeError: Cannot set properties of undefined (setting 'tableName')
Hi All,
Please i would like some help with solving this error
'TypeError: Cannot set properties of undefined (setting 'tableName')'
In the copy job activity editor, when i click on -> choose datasource , it shows the above error.
I have multiple copy job items and this error is seen in all of them, when i want to check the data source. I can access every other activity such as edit mapping, advance settings and so on.. also all copy jobs runs well and on schedule.
i have permission to see the data sources as i created the copy jobs.
Thank you in advance
Hi everyone, i believe this issue has been fixed as i can see my queries and can see all data sources.
14 Replies
- QMMFrequent Visitor
I'm having the exact same issue.
- hentoneNew Member
Hello, I am having the same issue
- J029
Advocate I
I did some further research on this, saw something about the error being with the Fabric UI as every other actvity is functioning well. I will raise a support ticket.
- TommyCroteauFrequent Visitor
I have the same issue, its now a know issue https://support.fabric.microsoft.com/known-issues/?product=Data%2520Factory&active=true&fixed=true&sort=published&issueId=1764
- J029
Advocate I
Hi everyone, i believe this issue has been fixed as i can see my queries and can see all data sources.
- AntonioPinedaRegular Visitor
HI, I am having the same issue just when the Copy Job is using a query. I know it's a know issue. Do we have an estimated time for it to be fixed?
Thanks!
- hentoneNew Member
Hello J029, the issue is not fixed on my side.
- TommyCroteauFrequent Visitor
Still not fix for me
- andysharpskyNew Member
We are having the same issue, it appears when you add a query to the copyjob. It works fine if a copyjob only contains tables.
- J029
Advocate I
Hi Everyone having this issue, indeed it was a problem with the UI and you can check out a temporary solution https://support.fabric.microsoft.com/known-issues/?product=Data%2520Factory&active=true&fixed=true&sort=published&issueId=1764
I believe this would work if you have just few copy job/one -off data pull. I think this issue affects copy job using queries, as the solution advises to delete the query settings from the JSON code. I was informed the solution to this issue will be released late next week.
Hopefully this helps 🙂- TommyCroteauFrequent Visitor
The solution is not useful. You have to delete every query and recreate them every time you want to update your copy job.
- J029
Advocate I
Yeah, hence it is a temporary fix. hopefully the update next week will fix the issue. 🤞
- J029
Advocate I
Hi AntonioPineda TommyCroteau hentone
I assumed this was working for everyone, apologies for that. When i spoke with the support team, i was informed this would be fixed end of this week. I would advise that if you don't see any query by end of day tomorrow or the weekend then raise a support ticket. I can confirm I can see my queries and data source. Probably it's a batch update, and will get to you soon. Hope this helps