Is there any way to pass a primary key ID of Major BO (ex Incident ID: 1234) to a new data in Supporting BO?
I am trying to create a Schedule (supporting BO) for an Incident (major BO). And since 1 schedule, which reflects 1 investigation for an Incident, sometime requires 2 manpowers with a same date, but different timestamp, so I would like to have that as a new data with the same Schedule ID, the same Incident ID, but different Technician ID; instead of creating duplicate fields for technician name and date/time which I found it's inefficient.
The way that I achieve it so far, under Schedule page, I create a link with run a one-step where that one-step will create a new BO (Schedule BO) and retain Schedule ID. However, I could not retain the Incident ID because it is basically triggered a new BO.
Have anyone encountered this scenario before? Or is there any other idea that could achieve this scenario?
Would it work to use a Join Table (Standard, but maybe Custom is better for you) link instead of the Default link in the relationship, and then enter a Join Reason as part of the one-step ?
Have you tried to store the value in a variable or user specific stored value so you can have it when you are creating the new BO?
I tried this solution, and it works! Thanks. The tricky part is I still need to link the data from supporting BO to major BO, and I couldn't use the one-step feature. Sorry I am still figuring out a way here.
If you are getting data form the supporting object and want to return to the major object you can do the following:
1. Capture RecID of main object ( I think this is already done in your stored var/variable)
2. While in the supporting object update a new Var/Stored val using a psuedo XML format
3. Using GoTo record to the main object using the RecID from the Stored Value/Var (Might have to use Stored Value here)
4. Use an update business object and in the field use the Psuedo XML Stored Value and the modifier Text Between and use the <Title> and </Title> so you only add the text you want for that field and continue this for any and all fields.
Its a bit janky but it does work.