Defaulting Values on Change Model

[awilkerson]

I am attempting to default the category and subcategory on specific change models. The issue I run into is that they are set to read only when I do. I simply need to default them and not set for the duration. 

What I have tried:

1. The record preset method. The values are ready only on create and submit.

2. I have also tried the UI policy. The UI policy adds another issue in that we have a script include that triggers off the category. Once I set the category, the subcategory is empty. The category is set to read only. 

[Chaitanya ILCR]

Hi @awilkerson ,

you can create an onLoad client script 

or you can update the dictionary default value (with some script)

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya

[Dr Atul G- LNG]

Hi @awilkerson 

Did you try setting it as the default at the model level itself, like shown below?

[awilkerson]

I did. That worked except for the fact that those values are now read-only. I need the ability to change them. 

[Dr Atul G- LNG]

Hi @awilkerson 

Now it's becoming contradictory. On one hand, you're saying you want to prefill values from the model to reduce manual effort, but then you're also saying you want to change those values later — which means you're not happy with what the model is providing.

If that's the case, then you shouldn't set that value in the model at all and instead ask the user to input it manually. The purpose of using a model is to reduce the time and effort required to fill out a change record — and it seems like you're trying to override that, which could lead to breaking the intent of the model.

My suggestion: think it through. Either use the value in the model or keep the field open for manual entry — but mixing both approaches will only create technical debt.