Hi all, I need help with something that I've tried to fix for the past two days. I have a master workspace and child workspace. The master workspace works fine, but the child workspace shows error: Grain identifier="Id" was not found in dataset "..." within the dataset attributes or referenced attributes and dates. I've tried and removed the table, but then the same error happened with other table. Does anyone have any idea what is the error? I have a workspace filter for the master and workspace data filter settings for the child

Hi Goran, I have been checking our logs for the last few days and I keep seeing errors relating to the same object:

errorType=com.gooddata.tiger.grpc.error.GrpcPropagatedClientException, message=Grain identifier='attribute/Space.Id/f221d0d2d5124e13a1394d565050013a' was not found in dataset='dataset/BookingOccurenceInformation/f221d0d2d5124e13a1394d565050013a' within the dataset attributes, or referenced attributes and dates.

This error indicates that the grain identifier

'attribute/Space.Id/f221d0d2d5124e13a1394d565050013a'

was not found in the specified dataset

'dataset/BookingOccurenceInformation/f221d0d2d5124e13a1394d565050013a'

. It seems that the attribute

Space.Id

is expected to be present in the dataset, but it is not available. To fix this error, you’ll need to ensure that the attribute

Space.Id

is correctly defined and available within the specified dataset

BookingOccurenceInformation

.

Hi Michael. Thnx for the info, I will double-check but the thing that bothers me is that the MasterWS workspace loads everything as it should. Also, the MasterWS is copied from another workspace that loads everything as it should. Just the children have problems

Can you tell me if you perhaps made some updates on your model in your MasterWS recently?

Recently yes, I deleted one of the tables that initially was causing problems, to see if it is the table or something else

And before this change, the models were identical? I think it might be best to compare the Data Models of the affected child workspace with the master workspace. Perhaps there is discrepancy in grain, attribute mappings, or filter settings that might be specific to the problematic ChildWS?

But doesn't the child workspace takes everything from the parent workspace? I have only created a Workspace Data Filter Settings for the child workspace nothing else

Hi Goran, just a few hints that might help with the investigation I believe: • the term “grain” refers to a primary key (or its component) and if I understand it well, the error is complaining that for dataset

BookingOccurenceInformation

the primary key contains attribute

Space.Id

but this attribute is not present in the dataset. ◦ does this sound right to you? Should this attribute/column be part of the primary key? And is it present in the dataset? ◦ you can also get the model definition from the API with

GET

API call to

/api/v1/layout/workspaces/{PARENT_WORKSPACE}/logicalModel

and then inspect the proper dataset and values of its property “grain” to see what is really there and if it is is expected. • before removing the table you mentioned above, was its foreign key part of the primary key of the other dataset? I can imagine a situation where you had a primary key consisting of several foreign keys and you removed one of the tables its foreign key was for some reason not removed from the primary key. • does the child workspace have any extension of the data model of the parent workspace or does it only inherit the parent model? ◦ you can check it with

GET

API call to

/api/v1/layout/workspaces/{CHILD_WORKSPACE_ID}/logicalModel

◦ if it returns just empty JSON it would mean that it is just using the parent model (which should work unless there is some bug I assume)

Great thanks, I will try to do this

Just FYI - the engineers have identified a bug and the fix will go to one of the next releases.

Great, I just needed to fix my thing and thank you so much that you identified the issue. The fix to use multi-column key is nice but not that urgent