Nested new records with gui for reference field

[agchoi]

I have a few custom tables that are related to each other. One of the tables has a reference list to another. This second table has a reference field to the third. When creating a new record for the first, it allows me to make new records for the second table but not for third table. The closest option I can see that is built into ServiceNow is the dynamic creation option but it only allows for one input. For the third table the record has multiple fields that should be populated differently record from record. Is there any way for the nested new record gui to bring up another one for the third table?

[Chuck Tomasi]

Hi Andrey,

I think I've lost track of what is happening manually and what you would like to happen automatically. Do you have any screenshots?

I re-read your original post and it sounds like you want to open a record on table 1, then table 1 has list field, using the magnifying glass, open the record selector & click New to create a new record on table 2. While you are creating a record table 2, you want to do a similar operation to create a record on table 3.

Is that correct?

Example: Open a user record, in the department field, add a new department, in the department selection window, create a new manager for that department.

How close am I?

[agchoi]

Yeah, your example is pretty much the idea of what I'm thinking of. In the Item field in the screen shot it should have an option to create a new record with multiple fields for this new record.

[Chuck Tomasi]

Hi Andrey,

The reason you cannot do this recursively is because you haven't saved the second level record yet. The reference field on the third level needs something to link to. There's no record, so there's no sys_id. That's why the Item field doesn't show a lookup (yet).

I hope that makes sense.

[agchoi]

What do you mean by third level? The third table doesn't have a reference field to the second table, it's one directional. The idea is that this is a PO system with the PO table referencing a PO Line table with the line table being able to reference an item so that if an item is commonly ordered it could just be selected rather than have all of the information retyped. So the line table has a reference to the item table but not the other way.

[Chuck Tomasi · Accepted solution]

Thank you for the clarification. My brain had the ordering backwards.

My understanding is that it comes down a user experience thing. If you are in a reference view creating a new record and want to do another lookup, having multiple popups could bit a bit of a mess and start looking like the Internet browsers in the 90s.