Showing results for 
Search instead for 
Did you mean: 
New Member

Patch Column Option Set Type Error



I am trying to patch a data in CDS, 


Patch(Inventories,First(Filter(Inventories,'Inventory Id' = ThisItem.'Inventory Id')),{InventoryStatus:"Available"} );Refresh(Inventories)

However, getting the error "The type of this argument InventoryStatus does not match the expected type 'OptionSetValue'. Found type 'Text' "


How do i patch the option set type? 

Helper I
Helper I

I too am facing the same error of "expected type OptionSetValue. Found type Number" when trying to Patch an option set to CDS.

My scenario is - I'm trying to put together a shipment form made of a number items and one of the parameters of every product is its final destination (there are 3) which is picked from an option set (presented in the canvas app with radio buttons).

All items are collected in a local Collection (ShipmentitemsCOL) and once all is set – clicking a button (OnSelect) will trigger the Patch under Forall, and create/update the records in the CDS entity.

Now, this all works fine with text/number or even lookup fields, but an OptionSet…..


Any help / hint will be very much appreciated.  🙏

I'm banging my head over this for three days and tried everything I could find but to no avail 😩



Hi @Avinoam ,


I found a solution for these option sets (It was working 2 weeks ago, before the update of the Power Platform 😆), so if you can try it and say me if the problem is solved, it will be great !


So please try to use the Dynamics 365 connector (Premium), so you will be able to pass true/false, integer and concateneted text instead of the Option Sets Values.


So my conclusion is that the connector for CDS is very useless


But what about Dynamics 365 Today ?

It is deprecated ?


Bests Regards,


I actually solved my problem by reverse engineering my app and found that my original input component which collected option set choice was not properly connected to the CDS option set and once that was fixed the patching was no problem. 

Your solution @Romsteck  may be a good one but as you yourself say the Dynamics 365 connecter is on its way to be depreciated (I told so by a Microsoft engineer).
anyhow, thanx for the answer and solution. 👍

BTW to the best of my knowledge the CDS connector is undergoing an extensive upgrade these days (Kepler project ?)

Helpful resources

Power Apps News & Annoucements carousel

Power Apps News & Announcements

Keep up to date with current events and community announcements in the Power Apps community.

Power Apps Community Blog Carousel

Power Apps Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Top Kudoed Authors
Users online (3,486)