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

Patch Column Option Set Type Error

Hi,

 

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? 

12 REPLIES 12
Frequent Visitor

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…..

2.png1.png

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,

Romain.

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

Announcements
secondImage

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Top Solution Authors
Top Kudoed Authors
Users online (17,212)