Handling @type and @baseType fields in Scripted REST API → Subflow mapping

abhis42
Tera Contributor

I’m receiving a JSON payload through a Scripted REST API and passing it to a subflow for further processing. The payload contains attributes like @type and @baseType.

 

However, when defining the subflow input, ServiceNow automatically converts @type to _type, which results in a mismatch and prevents me from mapping or accessing the original values correctly.

 

Is there a supported way to accept and map these @ attributes as-is within a subflow input? I’m intentionally trying to avoid receiving the payload as a raw object and handling it via custom script logic.

 

Any guidance or best practices would be appreciated.

 

Thanks in advance!

0 REPLIES 0