Right on time!

Basically you run into delegation issues when you use them. They are best used when working directly with Dataverse tables and/or modern driven apps. Best option is to create choice columns as a collection in your app or a separate list

Basically you run into delegation issues when you use them. They are best used when working directly with Dataverse tables and/or modern driven apps. Best option is to create choice columns as a collection in your app or a separate list

Your question is not so clear but here are other options to explore if you want to avoid using choice column: 1. Create your choice field on the App.Formulas propery using named formulas 2. Create a separate table (i.e. sharepoint list) for your choices)

@@PowerAppsTutorial Thank you for your response. You mean choice field or table in power apps? I'm not that much experienced with Powerapps yet. Do you have any videos that shows how to do that. We don't want to replace these choice columns with another SharePoint list for two reasons. 1. If we add another list for every choice column it makes a lot of unnecessary lists in the site. 2. If for example you turn one these these columns into list A on your SharePoint site and you link data from list A into list B by using lookup column you can't link that column from list A into list C anymore. Does it make sense?

Can you post your challenge on my FREE community for quick help: www.skool.com/power-apps-community

Yeah I am running into this issue with a project i am working on and dont know how to best remedy it.

What are you challenges?