Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Regarding the first part of your question<br> <em>"What I have in mind is to create a hidden field in Bookings that is populated when I choose one of the options from Discharge drop down and based on that field the record should shift the view in Bookings. But how do I populate the hidden field?"</em></p> <p>If the field is not on a form you can't set its value hence the following: I don't believe you can set a hidden field using a workflow. However there is a 'visibility' option on the form designer.</p> <p>I suggest you add your "hidden" field to the form. Then double click on it and toggle the "Visible by default" checkbox. This will hide the field from the user.</p> <p>You can then set the value of this field using a workflow.</p> <p>Regarding part two of your question<br> <em>I don't want to choose the record in Booking entity but directly update it from Discharge. There are some fields and their values common in both forms, can I create a relationship based on that</em></p> <p>You have a 1:N relationship however you want to set the related Booking Dynamically is this correct? You cannot select a Booking in the lookup field based on criteria from a workflow. You would need to use a plugin.</p> <p>If the Discharge has a related Booking (the Booking lookup on Discharge is already set) then you can use a workflow to either: 1) Set a field value (Using 'Update Record' in the Workflow steps) in the parent Booking 2) set to Inactive (Using 'Change Status' in the Workflow steps) in the parent Booking</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload