How to correctly implement Attributes tab on Customer Location screen (AR.30.30.20) using CRAttributeList?

Hi ​@bihalivan15 

This is a tricky scenario because Customer Location does not behave exactly the same as Customer when it comes to attributes.

While using CRAttributeList is the right direction, it’s important to ensure a few things are aligned:

• Attributes are tied to the NoteID of the entity (via CSAnswers)
• The DAC you are using (Location) must properly expose and use its NoteID
• Attribute configuration (via CSAttributeGroup) must match the correct EntityType and EntityClassID

Also, Customer attributes are typically driven by Customer Class, but Location is a separate entity, so attributes are not automatically inherited unless explicitly configured.

In many cases, just adding CRAttributeList is not enough—you also need to ensure the attribute mapping and data views are correctly set up in the graph.

You might want to double-check how the Customer screen (AR303000) wires this internally and replicate the same pattern for Location if your goal is to match its behavior.

You can also consider whether UDFs might be sufficient depending on the requirement, since they are easier to implement compared to full attribute framework.

Thanks!