Record Producer Ignoring Field Default Value When Creating Project

[Erik Nelson]

Hello!

We have a Record Producer (RP) being used to generate Projects and for some reason it is ignoring our default "Execution type" value, setting it to "Waterfall". In the dictionary entry we have it set to "Hybrid" and if a Project is created through the Project Workspace, it works properly. We don't currently have "Execution type" on the RP but I've tried adding and mapping to the appropriate field and it always sets the value on the Project itself to "Waterfall" regardless of the selection. it's not doing this as an update, it's doing it on insert of the record. I don't see anything in the setup of the RP itself (no Client Scripts, etc.) that would override a selection and I'm not seeing anything on the Project that indicates it would do this. Any thoughts or spots where I can look to find what's keeping the field from being set properly?

Thanks!

Erik

[Prashant Moily]

Hi Erik, 

Please share the screenshot with us, I have tested this in my PDI it works as expected.

[Erik Nelson]

I can see in the history of the record created that it's still defaulting Execution type to Waterfall, despite me selecting Hybrid. I don't think this is related to mapping though because we don't natively have the field available and the dictionary entry has the default set to "Hybrid".

[Erik Nelson · Accepted solution]

Because we got a solution from ServiceNow, wanted to share it here to hopefully save people some time. In our Record Producer, we're also applying a selected Project Template (project_template). When you create the template, it applies the Execution type and that will always be the Execution type applied when the template is applied in this manner. That field is not editable when it is set. The configurable resolution is to remake the templates if possible from a Project in the correct Execution Type. If you have too many templates to make that feasible, you can insert a line of code in the Record Producer "current.setValue("execution_type", "hybrid");" beneath the Template assignment. This will force the record to update again after the template has been assigned.