<#C029A3M079U|troubleshoot> Hi everyone, I'm tryin...
# troubleshoot
a
#troubleshoot Hi everyone, I'm trying to add a new Aspect to Dataset entity in the metadata-model-custome. The Aspect is
Copy code
namespace com.mycompany.dq

/**
 * Details about dataset Storage.
 */
@Aspect = {
  "name": "storage",
  "autoRender": true,
  "renderSpec": {
    "displayType": "properties",
    "displayName": "Storage Info",
  }
}
record Storage {
  format: optional string
  compression: optional string
  sizeInBytes: optional long
  fileNum: optional long
}
I can insert storage aspect successfully, but there is not Storage Info tab in the web page. Does anybody have the answer to slove the problem?
b
hey Yang! it looks like your new aspect is set up on the PDL correctly. have you gone through all the steps to add a new aspect as well? for example - adding your new aspect to the entity registry. here are some docs with info on all those steps: https://datahubproject.io/docs/metadata-models-custom/
a
@bulky-soccer-26729 Thanks for your reply. I do follow this doc https://datahubproject.io/docs/metadata-models-custom/. When Aspect of Storage only contains only one field, it can be displayed on the web, but it can't be displayed when it has multiple fields. Could you give me a example like my case or more detailed docs about renderSpec except https://datahubproject.io/docs/metadata-modeling/extending-the-metadata-model#metadata-annotations?
b
oh gotcha that's interesting and not something I would expect. I don't know of other docs around this piece specifically off the top of my head other than the general docs for A Custom Metadata Model. When you try to ingest the aspect with more than one field, do you see any errors at all in GMS? and on the frontend, if you open your network tab and find the
getDataset
graphql query when you're on the dataset entity profile you add this custom aspect to, can you look for the field
autoRenderAspects
? it should be in the payload like this (but with data in the list)