cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AccuFloDev
Advocate II
Advocate II

New feature "Relational data, option sets, and new features for CDS" makes some option sets completely unsuable.

I'm running into an issue using a CDS for Apps entity with a Global Option set.

 

When I attempt to set or filter on a value in this column, it will not accept ANY value.
Its almost as if the background JavaScript is not able to successfuly generate the enumeration.

This issue persists even when creating a form - I can set the Form's data source to the CDS entity itself, and when I add the option set column through the Field picker, it adds the data card in but it immediately has errors on the ComboBox (see image below):

Data Source for the FormData Source for the Form
Adding Option Set column to the form using built-in form editorAdding Option Set column to the form using built-in form editor
This is the error shown in the Data Card's Combo Box Items propertyThis is the error shown in the Data Card's Combo Box Items property
The error shown is telling me to add the entity "cra_af_lpgcalibrationreports", which is the internal display name of an entity I have already added ('AF LPG Calibration Reports').   Removing and re-adding this entity from the connections does not fix the issue.  I have even tried removing the PowerApps connectors and re-adding them, no dice.

An additonal problem I'm having which I think is related is if I try to do a LookUp or Filter on this entities Option Set Column - I cannot find the Option Set Enum to compare it to. 

Nothing that the intellisense recommends works...only errors:
Error-03.png

At this point I think this is a bug.    
Anyone from the Microsoft Team able to review this? 

2 REPLIES 2
v-yuxima-msft
Community Support
Community Support

Hi @AccuFloDev 

 

Do you fix your issue?

Do you firstly create one option set?

option1.PNG

option2.PNG

option3.PNG

 

More information:

common-data-service/custom-picklists

 

Hope this could be helpful.

 

Best Regards.

Yumia

Hey @v-yuxima-msft ,

I resolved the issue by ensuring the other errors in the app were resolved, I think the text parser was having trouble enumerating variables due to existing errors.

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Power Apps June 2021

June Power Apps Community Call

Don't miss the call this month on June 16th - 8a PDT

Top Solution Authors
Top Kudoed Authors
Users online (55,717)