I am able to pull the dataset in edit mode and apply left join , Joined data looked fine in dataset level but when i am trying to publish or refresh the entire dataset , it is sql exception error throwing error .
Joining based on JUR and LE . Apart from this there is no after common columns to join.
Error-
A problem occurred during the refresh of your SPICE dataset for the account “atx-datavis”. Here are the details:
A general SQL error occurred. This error can be caused by query timeouts, resource constraints, unexpected data definition language (DDL) changes before or during a query, and other database errors. Check your database settings and your query, and try again.
1 Like
Hello @srivprag, welcome to the Quick Community!
Can you provide some information about the datasets? I am curious, what is the source of the 2 tables? Are they coming from the same database or different data sources?
If they are the same database, I would highly recommend running the join either in the source, or in custom SQL in the console. If joining datasets, I only recommend using the internal join tool when they are coming from different sources.
Also, do these datasets exist on their own in Quick Suite, or do you only import them together in this join? You may see better results if you make 2 individual datasets first. Make sure the source dataset for the table data_fng_control is set to refresh before the vis_fng_hc dataset. Then, set the joined dataset to refresh after both of those are completed.
2 Likes
So one table source is codap_prod and another is DCCollector , source is different but both the dataset is imported in Quicksuit and then i opened one dataset and then edit it and imported the another one and joined as shown in snippet.
Can you please give more idea on-internal join tool that i can use?
Hello @srivprag, are there any differences in the formats of the 2 fields you are joining? A good place to start for debugging would be to try joining the 2 fields separately and see if there are any issues refreshing the dataset. Maybe one of the 2 columns is causing a problem that is harder to see when we join with both fields.
2 Likes
The format is same in both the tables- both strings. It is like many to one relationship. One table has multiple LE as well as JUR but in second table one common row .Based on this i am pulling preparer and reviewer details from second table
Adding one more point -
I tried adding vis_fng_hc dataset with other dataset and this one is working as expected.No issue in joining and publishing .
