Can I have two entities' field in the same form? Upstream & Downstream entities?

[ChuanYanF]

Dear experts,

I would like to have two entity fields in the same risk event form, where I created a relationship between upstream and downstream entities. Since reference field cannot set up a dependent value in the dictionary, how can I make the dependency works on the two fields, where if this particular upstream entity is selected, only the downstream entity that is tied to this upstream entity will be populated in the downstream entity field?

[ShafrazMubarak]

Adding another entity will be considered as a new field to the risk event table. Please note that all the dashboards and reports, other upstream process will consider the actual entity field. the newly added field will not be considered unless you have modified them. 

Once you create a new field, you can add a relationship as dependent for the actual field. For this, you need to make sure you have already established the parent - child (upstream - downstream) entity relations in system.

BTW, what is the actual business need for creating another entity in this real case for risk events

[ChuanYanF]

Hi Shafraz, 

Thanks for the reply, so what you are saying is that the new entity field (downstream) is consider as a new field but i make it as a reference to the entity table as well to try and get the downstream entity. So currently in my case, the department and the subdepartments are the entities and department will be (upstream_profile) and the subdepartment will be the (downstream_profile), so in my case, when users want to select the upstream entity (department) the downstream entity (subdepartment) should populate based on the upstream entity as in the specific subdepartment of this department. Cause if I use the reference to the department it does not have a relationship between the entity table and the department table, that is why I chose this approach to get the upstream and the downstream entity.

[ShafrazMubarak]

So at the end of the day, do you need the risk event to be assigned against the sub department? 

If so, the parent department will act as a quick referential filter for selecting the sub department. In that case, you can take the parent department entity as the new field.