Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
6 replies
Subscribers
11 subscribers
Views
3081 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
When creating a Record Type you are asked to select a data store and the entity.
mikec
over 9 years ago
When creating a Record Type you are asked to select a data store and the entity. How can you show data in the Summary View when the data comes from 2 different entites in the same data store? For example I have vendor details that are stored in the vendorcdt entity and I have contact information stored n the vendoracctmgmtcdt entity. Both entities are in the vendorDS. I want to show the vendor details in one column and the contact info in the second column in the same section.
OriginalPostID-137858
OriginalPostID-137858
Discussion posts and replies are publicly visible
0
mikec
over 9 years ago
To add: I am thus needing to hit two different entities but in the record type you are only allowed to select a single entity.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
priyal.patel
Appian Employee
over 9 years ago
You can only use one entity as the one your record is based off of. You will have to call all other data using query rules or query entity rules.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mikec
over 9 years ago
ah, ok thanks
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Steve
over 9 years ago
Mike, assuming each entity has it's own table and there's a 1:1 relationship you could create a database view combining both and define a third datatype with the view as it's source table which has all of the data you need in your record type.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Tim
Certified Lead Developer
over 9 years ago
Hi Mike, one of the big advantages of SAIL and Records is the ability to bring data in from multiple sources so consider how you users will navigate from record to record in a natural flow. If you have multiple contacts per vendor you could create an additional view to display a list of these contacts with each row having a record link to navigate to the contacts record type where you can perform context sensitive actions like updates etc.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
PhilB
Certified Lead Developer
over 9 years ago
To add to this, if you're looking to combine data from two entities in the list view (rather than in the view of a single item), it's worth creating a view as Steve suggests as otherwise query rules used in the SAIL list view are called repeatedly and so can result in a list view that takes a long time to load.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel