ValuesAllowed (field) Property

(0) Share

Report

Posted on by antmas

Community,

I've seen that the ValuesAllowed Property is Non-Customizable.

Has anyone found an effective workaround to this limitation?

I was hoping to use this to filter a list of ENUM choices based on user selections made elsewhere.

It'd be nice to be able to manipulate this like the VISIBLE Property, for which we can have it match a Boolean elsewhere (I know that ValuesAllowed isn't boolean).

Thanks,

Anthony

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (8)

Answers (1)

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hi

it's non-customizable

learn.microsoft.com/.../devenv-valuesallowed-property

DAniele

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,055 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi, The only solution now is to add repeated Enum fields on the page, then set different ValuesAllowed Properties for them, and then control which value is displayed through the conditions of the Visible property. . . It's a little troublesome. . . .

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Nitin Verma 21,794 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi,

This is property not available to customize, you can customize your solution to achieve the requirement.

Was this reply helpful? Yes No
antmas 60 on at

Like (0)

Report
Copy link

Link copied!

ZHU,

Before posting my question, I did consider your method (saw it in a separate post / answer).

That seems like a good solution for some cases.

However, in my situation, there are too many possible Enum outcomes to make a field for each.

Thanks as always for the thoughtful reply,

Anthony

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,055 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi, If there are too many values in your Enum, I suggest not to use the Enum type, but consider creating a table to manage them. In this way, more things can be done in permission or code.

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Verified answer

Muaaz Deyab 39 on at

Like (0)

Report
Copy link

Link copied!

I think you can create new Enum and field and map them to the original ones like This:

enum 90000 MyEnum

{ /// create enum with the same values of the original One

Extensible = true;

value(0; MyValue)

{

}

value(1; MyValue1)

{

}

value(2; MyValue2)

{

}

}

tableextension 90000 MyExtension extends Customer

{

fields

{

field(90000; MyField; Enum MyEnum)

{

DataClassification = ToBeClassified;

ValuesAllowed = 1, 2; // add the allowed values here

trigger OnValidate()

var

myInt: Integer;

begin

rec.Validate("original Field", MyField); // validate the original field

end;

}

}

var

myInt: Integer;

}

I don't know if it is a good solution, just trying to help.

Was this reply helpful? Yes No
antmas 60 on at

Like (0)

Report
Copy link

Link copied!

ZHU,

This seems like wise advice, and I will consider it if I cannot find another way to accomplish the same goal.

Thanks again,

Anthony

Was this reply helpful? Yes No
antmas 60 on at

Like (0)

Report
Copy link

Link copied!

Muaaz,

Thanks for the suggestion.

Perhaps I am missing something, but I don't see where the allowable selections become dynamic.

Based on the docs and multiple replies, it doesn't seem doable.

Thanks for the suggestion.

-Anthony

Was this reply helpful? Yes No