InsertOptionValueRequest works on local dev machine but fails on server

(0) Share

Report

Posted on by Fedorov

I have written some code that programmatically creates a new optionset value in a multiselect optionset.

The code works fine when executing on my local machine (which points to Dynamics 365 development server).

This code will run in a plugin and when I upload the plugin to the development server and perform the action that triggers the code then the code fails with a null reference exception on this line:

var resp = (InsertOptionValueResponse)_service.Execute(insertOptionValueRequest);

I can't figure out why, if anyone has any input it would be much appreciated.

InsertOptionValueRequest insertOptionValueRequest =
                        new InsertOptionValueRequest
                        {
                            AttributeLogicalName = "releye_salesexcellenceassessmentforms2",
                            EntityLogicalName = Lead.EntityLogicalName,
                            Label = new Label(text, 1033),
                        };

                    var resp = (InsertOptionValueResponse)_service.Execute(insertOptionValueRequest);

All responses (2)

Answers (1)

Suggested answer

Fedorov 40 on at

Like (0)

Report

RE: InsertOptionValueRequest works on local dev machine but fails on server

I just got it to work. The code was actually executed in the CustomApi context.

But when I moved the function to instead execute on the update (async) of another field where we store the text (dont ask why..) then it works fine...

Values will be created very rarely and the customer really wanted it to work this way....
Verified answer

Guido Preite 54,077 Moderator on at

Like (1)

Report

RE: InsertOptionValueRequest works on local dev machine but fails on server

depends on how the plugin is registered. If is registered as running in the user context (the default) the user needs to have the right permissions (like System Administrator or System Customizer) in order to add an option.

However I strongly advise against creating optionset values on the fly, they are not made for this scenario, is better to create a custom table and a lookup if the user needs to create values.