This week’s release of Blueprint has delivered the much anticipated ability to take a multi level class and be able to use fields from that class, regardless of level, to create views in blueprint.
Imagine that you have a service that is going to return you an account structure like this:
- Account
- AccountNumber
- AccountID
- AccountType
- PrimaryContact
- LastName
- First Name
- Phone
- Address
- Address Line 1
- Address LIne 2
- City,
- State,
- Zip
- Additional Contacts (list with the same structure as contact)
When authoring a view (collect info step) in blueprint, you can now select fields from any level of that structure. When you encounter a property that is another embedded one, you can drill into it and select attributes as necessary from that structure.
This will add those individual values directly to the page for viewing.
You can also select a node like additional contacts, which is a list and it will automatically display those records in a list structure.
In the setup below, I selected the node for primary customer’s address, the primary customer, the additional contacts and the selected three account level fields.
What I got was this:
Most importantly, you are not limited to displaying all fields from a node, you can select individual fields as needed to build out a view that only includes what you actually need. But, when you choose a node, you will get a grouping with a header that groups the content for that node.
What that means is that we can now author blueprints that include UI that aligns with our target state data model, significantly reducing the amount of effort required to make the views in your application production ready.
3/9 Update: This capability only applies to properties defined as embedded data, it does not apply to properties that reference classes on the data and integrations tab.