One record producer with two target tables?

[Ganeshm1]

Hi All,

Hope you are doing good. 

I have scenario, is there anyway to use one record producer targeting two different tables?

Example:
I have a record producer with variable called 'target table', with options 1. Incident, 2. Problem.

When they submit the record producer with target table = incident. I want to create Incident record.

Similarly when they submit the record producer with target table = problem. I want to create problem record.

I know people may suggest to create two record producer in this case but just curious to know is there any way to achieve this functionality. 

Let me know your thought on this. Thank You!

Best Regards,
Ganesh

[Ankur Bawiskar]

@Ganeshm1 

why would someone use record producer to create problem?

1 record producer will have only 1 target table

you can always use record producer script to manipulate data in other table.

OR
You can use a catalog item and then allow user to submit and then based on table selected create PRB or INC using workflow or flow designer

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Ganeshm1 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Dr Atul G- LNG]

Hi @Ganeshm1 

One Record Producer (RP) can target only one table. Also, what you're trying to do with variables like Incident/Problem is not a good use case. If your goal is to create multiple records from one RP based on a variable, that’s not ideal.

The reason is that ServiceNow already provides separate RPs for Incident and Change. A Problem record, for example, should be created by a fulfiller—not by the end user. That’s also why there's no OOTB RP for Problem.

So, I recommend following the system’s out-of-the-box design.

[AndersBGS]

Hi @Ganeshm1 ,

As @Ankur Bawiskar mentioned, you can have a record producer script to manipulate the input to a record producer, so you can create a ticket in two different tables based on input.