We have not received a response from you. Please let us know if above responses clarified all the queries. Otherwise, let us know and we will continue to engage with you on the issue.
Please do consider to click on "Accept Answer" and "Up-vote" on the post that helps you, as it can be beneficial to other community members
Hi @PhilBrammer,
We have not received a response from you. Please suggest if above suggested details are helpful. Otherwise, let us know and we will continue to engage with you on the query.
Please do consider to click on "Accept Answer" and "Up-vote" on the post that helps you, as it can be beneficial to other community members.
Thanks @VaibhavChaudhari for sharing the answer.
Hi @KrishnaNageshKukkadapu,
We have not received a response from you. Are you still facing the issue? If above answer helped you or you found a solution, would you please share it here with the community. Otherwise, let us know and we will continue to engage with you on the issue.
Thanks.
@JohnAherne-0132 - Our team will share the update and details once we hear back more details on the fix from Product team. Thank you!
Welcome to Microsoft Q&A Platform. Thanks for posting the query.
In order to investigate further, please share pipeline run id by running pipeline with the source columns that are partially detected which will help our team to access logs and will share more insights on the issue.
Looking forward for your response!
Thanks @FelipeRegisESilva-0968 for sharing the details. I will share the same with the internal teams for further investigation and get back to you once I hear from them.
Stay tuned!
Thanks @FelipeRegisESilva-0968 for your patience. Product team confirmed that query is odata query, not sql query and suggested to try with table and let us know if all columns are showing up. Also, refer this document for additional details.
If the columns are still missing, could you please list the columns (including type) that are missing? Please note that the complex types (link, person, group, etc) are not supported.
Looking forward for your response!
Thanks @FelipeRegisESilva-0968 for sharing more details. I will check with product team and come back with you once they share any more insights on the same.
Thanks @FelipeRegisESilva-0968 for posting the query. Product team suggested to check in list setting page and to create sample list to figure out the data types in SharePoint list. Later, they can be compared with compatible datatypes in this document.
Please let us know the details once you are able to check the type of the missing columns.
We have not received a response from you. Are you still facing the issue? If you found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.
Hi @Gobie-8269,
Thanks for your patience. I checked with internal teams and they suggested an existing issue with using decimal fields with precision>28(Fix will be deployed in few months). Workaround they suggested would be to use convert to reduce the precision to 28. Please let me know if you are using any decimal fields and if so, can you please do this fix and let us know if this helps.
Hi @sakuraime,
Welcome to Microsoft Q&A Platform. Thanks for posting the query.
Yes, it will work only if the table does not exist in dedicated SQL Pool. Currently, it does not support append or merge. I understand the feature gap and challenges in additional code required due to this limitation. I reached out to product team if there are any plans in pipeline to implement the same. I will get back to you as soon as I hear from them.
Stay tuned!
Welcome to Microsoft Q&A Platform. Sorry that you are experiencing this issue.
I have reached out to our internal teams to understand the root cause of it and will get back to you once I hear back from them. Thanks for your patience!
Thanks @satishumapathy-7150 for confirming the solution. Unfortunately, the escape character support is not yet available in synapse while loading using Polybase. As per my understanding, different delimiter needs to be used as string delimiter that can identify values with row delimiter in it Ex: single quotes since double quotes can also exist in the data as a valid value. Also, I would recommend you to create idea in feedback forum. All the ideas shared in the forum are closely monitored by Synapse product team and will be implemented in future.
Hope this helps! Please let us know for further queries and we will be glad to assist.