Replies posted by PD5
Okay I have tried Joseph’s suggestion and unfortunately it does not work as the data model now complains that there are multiple paths to the shared date dimension: refund table → refund created date column → shared date dimensionrefund table→ order reference column → order → order created date column → shared date dimension Maybe I’ll create another table for refunds that isn’t linked back to the orders table and use that to link back to the shared date dimension.
Thank you for your quick reply Moises.I was just deleting the fields using the standard data model editor previously, so I tried your suggested method of using the MAQL DDL editor and that did the trick.After deleting the necessary fields this way, I could add new fields using the standard data model editor and it published just fine. Thanks again.
Hello, I have another quick question regarding this issue.I have successfully saved the updated data model, but now when running a data load, it fails with the following error: Reason: Missing reference key specification for attribute "attr.products.productattributecolour" Where attr.products.productattributecolour is one of the removed fields. I think this is due to metrics or calculated attributes that make use of this field. Is there a way of easily removing anything that references these fields or should I go through all metrics etc by hand to remove them?Or is this error due to something else? Thanks again
This error generally indicates that the model is in an inconsistent state. You may need to try running synchronization command to fix this. Could you please try and let us know if it helps? Thanks Joseph, I've just tried this but unfortunately I’m still getting the same error when running the data load.
Hi Moises, thanks for getting back to me. I tried running the commands again and resynchronising but I’m still seeing the error.I also tried removing and recreating the workspace but the problem persists.I think this issue occurs if I clone a workspace, then import a data model over the top of the cloned model. I even tried editing the exported Json file to remove the fields and their mappings that I don’t need. This works and I can import the model and save it successfully, but on data load I get the same error aboveMissing reference key specification for attribute "attr.products.productattributecolour"even though that field is not in the Json at all.The reason I am doing this is that I’m trying to figure out a way of setting the field mappings on a cloned workspace without having to manually type each field in to the model using the UI. Is there another way I could do this?
Thank Iva, I though this was the case but just wanted to check.I would like this feature as it would make it slightly easier for dashboard users to set the value of variables without having to go to the manage/variables page.I think it would be useful for quickly changing a variable and seeing the results in a report. e.g. a report shows a list of sales and the commission paid on each item, with the commission percentage stored in a variable. It would be useful for the person viewing the report to be able to change the commission percentage on the report and see the results instantly.
HiThank you for your detailed response. I just checked the assigned fields again and found the issue. One of the added fields mappings was slightly misspelled with a missing underscore. Correcting this allowed the changed to be saved successfully. Thanks again for your help.
Already have an account? Login
Login to the community
Sign in with your community account. This is different than your login to your GoodData account. Don't have a community login? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.