Optionset in User defined Types

(3) Share

Report

Posted on by deseye

In User-defined Types:

Is there a way to define a User-defined Type for option set. I have tried defining the "OptionSet" or using "UntypedObject" itself. Using the optionset is invalid syntax and using "UntypedObject" is giving error

"Incompatible type. The 'TaskStatusCR' column in the data source you’re updating expects a 'UntypedObject' type and you’re using a 'OptionSetValue (RequestStatus (Client Requests))' type"

ColTaskType := Type({
    TaskStatusCR: (RequestStatus (Client Requests)),
    TaskStatusPTD: UntypedObject
})

Categories:

Experimental features

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @deseye

What are you trying to do this in? Is this a PCF control or?

Was this reply helpful? Yes No
stampcoin 5,166 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @deseye,

Type is experimental feature...
Did you consider using clearcollect function, or combine set() ?

Was this reply helpful? Yes No
ronaldwalcott 3,906 Moderator on at

Like (0)

Report
Copy link

Link copied!

Why would you try to create a user defined type for an option set. How is this option set going to be used?

Was this reply helpful? Yes No
deseye 48 on at

Like (0)

Report
Copy link

Link copied!

@ronaldwalcott @stampcoin @Michael E. Gernaey

thanks for your responses.

Currently, I use a button to trigger an operation, but I want to replace this with a user-defined function instead of relying on Select(Button).

Inside the button’s logic, I use Gallery.Selected to extract a record from the gallery and perform some operations on it.

However, when attempting to replace the button with a user-defined function, I need to pass Gallery.Selected as an argument. The challenge is that my function requires a user-defined type for the argument, but since the collection is a manipulated version of multiple data sources, it does not directly match any existing entity schema.

How can I properly define the function argument type to match my transformed collection structure?

Was this reply helpful? Yes No
ronaldwalcott 3,906 Moderator on at

Like (0)

Report
Copy link

Link copied!

Sorry but you would have to provide way more details than that to expect any feedback which could help.

Are you essentially trying to create dynamic collections with unknown types at runtime?

Was this reply helpful? Yes No
stampcoin 5,166 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @deseye,

since not much info from you project. I try my best:

Have you tried use it in App.Formulas ?

see below code.

TaskStatusCRType := Type({ RequestStatus: Text, ClientRequests: Text }); TaskStatusPTDType := Type({ Property1: Text, Property2: Text }); ColTaskType := Type({ TaskStatusCR: TaskStatusCRType, TaskStatusPTD: TaskStatusPTDType });

if that works, then you use ParseJSON for the next action.

my point is construct your data as JSON, then you can utilize ParseJSON,

OtherType= ParseJSON( Tasks, ColTaskType) AddColumns(OtherType, isTaskClosed, True)

please read this article user defined types

Was this reply helpful? Yes No
Suggested answer

w.p 8,345 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@deseye

ColTaskType := Type( { TaskStatusCR: fxTaskStatusCR, TaskStatusPTD: UntypedObject } ); fxTaskStatusCR := Type( { val1: Text, val2: Text, val3: Text } );

Was this reply helpful? Yes No