Another problem that I am facing is that I can't add description, tag or term in an element which is under an array or a struct in a dataset... The error that I am getting is this:

Update Failed! Failed to update urn:li:dataset:(urn:li:dataPlatform:dbt,gluegen.raw_events_testapp06.eis_motorquote_2,DEV) & field [version=2.0].[type=struct].[type=array].[type=struct].vehicles.[type=string].uuid. Field [version=2.0].[type=struct].[type=array].[type=struct].vehicles.[type=string].uuid does not exist in the datasets schema.

hmm so this happens when you try to add a description to a nested schema field here?

yep !

very weird, I'm not able to reproduce this situation myself locally. when you make the request to change it, what is your payload like? for example, your

resourceUrn

should be the urn of the dataset. then the

subResource

should be the fieldPath of the nested field her ie.

vehicles[].abi_cd

so I tried adding a description into a nested element

what does the payload look like when it's parent doesn't have []? also what does the schema of your dataset look like? something is getting thrown off here because that

subResource

field in your payload is certainly off. You should be able to see a request for

getVersionedDataset

and inside of the response you should see the list of fields with their `fieldPath`s

hey @bulky-soccer-26729, sorry for the delayed response. The payload when the item isn't nested(that works):

okay gotcha - yeah as you can see the

subResource

in the payload should probably just be

payment_details.payment_plan_cd

but instead has

[version=2.0].[type=struct.[...

as well which certainly seems wrong. could you reload the same page with your network tab open and find the graphql query

getVersionedDataset

and should be the "Preview" tab to see the response. I'd like to see your schema fields which should be in that response

the only relevant query i can find is getDataset

are you on the schema tab when you refresh the page? you should be seeing a getVersionedDataset that actually contains all of the fields. However if you expand on

schemaMetadata

>

fields

that should do the trick

thanks @bulky-soccer-26729!

is this happening when you try to add a description or something to any nested field on any schema?

yep

and are all your nested fields shaped like this? with one parent and the children defined under

nativeDataType

up there

let me see..

yup yup - something weird is happening with however you're getting your schemas into datahub or something related. I believe we expect fieldPaths for schema fields to be in the shape of

parent.child.grandchild

etc. and we use that to determine rendering as well as how we're updating the fields. so you can see in your original error that it's saying that field doesn't exist but it might be because things are inconsistent or that syntax in a field is breaking something

so, what do you suggest?

i'm actually going to ask around and see if anyone has seen anything like this before! i'll be back soon with some backup hopefully

Thank you @bulky-soccer-26729 !

for debugging purposes - what version of datahub are you on?

0.8.41 when we were discussing. I just upgraded to 0.8.44 and it is still there

okay gotcha - and you've reingested your data since upgrading?

nope

so maybe one of the children of

premiums