A client asks you to store work location information for their employees. The client mentions that multiple employees may be assigned to multiple work locations.
Which type of database relationship is the client describing?
A client asks you to store work location information for their employees. The client mentions that multiple employees may be assigned to multiple work locations.
Which type of database relationship is the client describing?
The client describes a many-to-many (M:N) relationship. This is because multiple employees can be assigned to multiple work locations and vice versa. Each work location can have multiple employees, and each employee can be assigned to multiple locations. Managing such a relationship will typically involve creating a junction table to handle the associations between employees and work locations.
Many to Many doesnt exist in appian.. while readin it says many employee many location.. so get an idea as a developer. a employee can only work in many location.. so that is 1:N
It does exist actually. If you create a new table in the database to save the relationships with employees and works, that would be the many to many relationship. Then, in Appian, you'd just need to create the CDT or Record Type for the table and create the relationships over there.
While the best practice of Appian is to NOT make database amendments manually... This is about what is possible WITHIN APPIAN, not what is possible with a workaround... I vote 1 to many. An employee is a "individual" which could work in multiple locations. But there are no multiple persons which are the same person...
Absolutely C, the quesition is asking which relationship describing, it's not relevant to the question whether Appian has this relationship or not. Even this page describe a case similar to this question: https://docs.appian.com/suite/help/23.2/CDT_Relationships.html#many-to-many-relationship Many-to-Many Relationship An example of this would be an application to manage Employees and Projects. Each Project has a team of multiple Employees, but a given Employee might currently be on more than one Project
Many to Many
Answer should be C
Many to Many it is
Many to many does not exist in Appian natively. The answer is A, one to many.
The best practice of Appian is to NOT make database amendments manually... This question is about what is possible from WITHIN APPIAN, not what is possible with a workaround... Since many to many doesn't exist in Appian, I vote 1 to many. An employee is a "individual" which could work in multiple locations. But there are no multiple persons which are the same person...
I think C is correct
Hi friend, How many questions from the official Appian exam did you get from this exam?
Many to many in appian no exist. answer is A