Answered

Build Option Set from Flow or dataflow

(0) Share

Report

Posted on by notj

782

Is there some way to create an Option Set in the CDS from a dataflow, import, Flow, or anything else other than manually typing every single option out? It's a pretty cumbersome interface when you compare it to other systems where you can copy and paste multiple options at one time.

I have an Option Set I need to populate with over 100 options and I really don't want to click Add new, delete "new option" label text, copy, paste, click Add New, etc. for every single one of them.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Ben Thompson 1,400 on at

Like (1)

Report

Try https://www.xrmtoolbox.com/plugins/OptionSetEditor/ from Memory this will allow you to export option set values as csv / excel files and allow you to edit and then re-import them.

Optionsets are metadata within Dynamics designed to be stored in Solutions to provide static data values (the argument was that dynamic values are best treated as entities a that offered greater flexibility).

It does mean that editing Optionsets is a lot harder than it should really be the case but there is little likelihood that things will change as optionset values have their own meta data level XRM messages

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report
Hi @notj, other options are:
Export an unmanaged solution with that optionset field, unzip the file, edit the customizations.xml and manually add the other items. Rezip the file and re-import into your environment.
There's also another tool in XrmToolBox named Attribute Factory which is helpful to bulk create your attributes for an entity: https://www.xrmtoolbox.com/plugins/Javista.AttributesFactory
Hope this helps...

Was this reply helpful? Yes No
notj 782 on at

Like (0)

Report

@EricRegnier @ben-thompson thanks guys. It looks like I have a couple options, even if they are a little cumbersome. I got fed up and just made it a separate entity. Good to know options exist for future reference though.

Was this reply helpful? Yes No