https://www.gooddata.com/ logo
Join Slack
Powered by
Hey, just tried to save a SQL dataset in the data ...
# gooddata-cloud
m
Hey, just tried to save a SQL dataset in the data tab and I get the following error 🧵
Why is that?
Copy code
{
  "detail": "Only unique entities are allowed for the operation. Non-unique entity IDs=[Identifier(untitled_sql_dataset.type)/Workspace(079ded41cc594b478b3e76bf04295715)].",
  "status": 400,
  "title": "Bad Request",
  "traceId": "bd793cfbb9f69ef9"
}
i
Hi Menelaos, Could it be possible that your model already contains a dataset with the same name as the one that you are trying to save now?
Also, please double-check if you named your new dataset - the title cannot be empty.
✅ 1
m
Hey @Ivana Gasparekova, thank you for your response. Would you be able to explain further what "dataset" means? The new model, is a query that retrieves data from other models inside the schema.
j
The concept of GoodData dataset is described here: https://www.gooddata.com/developers/cloud-native/doc/cloud/model-data/concepts/dataset/ True is that SQL datasets are not mentioned there, I am raising an internal issue to our DOC team. But the concept stays the same - they are a logical representation of database tables OR sql queries(SQL datasets). They decouple you from the physical model and provide you "logical" features such as what is fact/attribute/label/date dimension, define business titles/descriptions, define granularity(~primary key). relations between datasets(even M:N), etc.
m
Thanks @Jan Soubusta for your response. How should I follow up on this? Should I wait for further assistance from your side?
i
I assume, there is no need to wait for our Documentation team till they update the article mentioned by Jan. Or do you have some trouble with setup of the title, please?
m
I've setup the title @Ivana Gasparekova and I still get the same error
Copy code
"content=ldm status=400 error={\"detail\":\"Only unique entities are allowed for the operation. Non-unique entity IDs=[Identifier(training_suggestions.type)/Workspace(***)].\",\"status\":400,\"title\":\"Bad Request\",\"traceId\":\"21d98004472fdad7\"}"
j
I don't see the full SQL statement, please, copy&paste it here
m
Just sent it in DM, for security purposes
✅ 1
i
In the meanwhile, you can review this article.
m
Thanks @Ivana Gasparekova. This is exactly what I took as an example to create the SQL dataset I'm talking about.
i
Cool, thank you for the confirmation. I hope that Jan will help you find the reason of that error.
🙌 1
m
Following up on this I successfully resolved the issue after @Jan Soubusta’s help. Thank you 🙌
Another issue I have though, just tried to retrieve from the database a uuid field, but getting a message that it's unsupported. How is it possible that you don't support uuid type while it works for the rest of the fields? Thank you in advance
j
Do you use it in a SQL dataset or in a standard dataset?
m
In a SQL dataset. In the same I DMed you yesterday
j
Let me check it internally
It's a bug, sorry for that. Will be fixed today and released as soon as possible.
m
OK great, thanks for that. Please let me know when this is fixed?
j
Should be released this month, July 27th. Sooner, you could test it with our single container community edition, tag dev_latest is released every Wednesday.
m
Well, this is quite blocking since we would need to release the report earlier than this date. Would you be able to provide a workaround on how to produce the following report? We have a table in our db called xxx and we do the SQL joins I've DMed you in order to produce the report. Up to now, I've added them as rows in the report I want to produce, however, I think I would need to add the primary_key to the metrics part in order to identify each row, correct?
j
CAST the column to VARCHAR data type
👀 1
Open in Slack
PreviousNext
Powered by