How to limit a "Spare Field" field to a maximum of 18 characters in a service item parameter on the web portal?

Did you try to limit the data length for that column in Designer? You can specify a max. length there.

Hi Markus, by doing that, wouldn't i be limiting all places that use this table in the web portal?

You would limit the column to all entries in PersonWantsOrg.CustomProperty02 and ShoppingCartItem. CustomProperty02, but maybe that is not what you intended.

You've hit on my concern. I need to limit the field's length exclusively in this one instance, as I cannot allow it to impose restrictions on other parts of the system that rely on PWO.

Btw, thanks for helping me out.

I've identified two potential solutions. I could apply a formatting script directly to the customproperty02 table, but it would need a condition to only affect the specific service item. Alternatively, I could create a request property without the legacy definition, as it offers a value calculation option. However, I'm unsure how to write the necessary code for that calculation, as there are no examples available.

I always try to look at the table DialogParameters for some samples. There is a guide on our GitHub page as well. https://github.com/OneIdentity/IdentityManager.ApiSdk/tree/v93/request-properties 

In your case you could use the following code in the validationScript of the new style parameters.

Dim strVal = Convert.ToString(Value)
If Not String.IsNullOrEmpty(strVal)
	If strVal.Length > 18 Then
		Throw New ViException("Maximum length is 18 characters.", ExceptionRelevance.EndUser)			
	End If
End If

Thank you so much!

It did work, but also, the new Request Property only work to the new Angular web portal, and the version of mine is outdated, so it only worked in the API server.

Yes, the new request properties are only supported in the API Server based Web portal and not in the legacy Web Designer based portal.

Yes, the new request properties are only supported in the API Server based Web portal and not in the legacy Web Designer based portal.

Well, thanks again for the detailed explanation and the link to the GitHub guide! I really appreciate it.

For now, we aren't able to update our portal to the Angular version, so I'll need to explore other solutions that are compatible with our current setup.

The solution you provided using the new Request Property worked perfectly in the API server, which is fantastic. However, you're absolutely right; it only works with the new Angular web portal.

Even so, your input was incredibly helpful and clarified a lot for me. Thanks again!