Hello all,
I'm relatively new to using dataverse within my canvas apps and have been primarily using Sharepoint, so hopefully, these are easy question for someone to answer. My environment is GCC which does often mean things work a little differently.
I have a dataverse table that I added a lookup column using the User table. Within dataverse, this works perfectly (even if the formatting is different than how SharePoint would display the name). Next I created a canvas app and added the dataverse table as a source, created a page and added a classic form linked to the dataverse table which imported all of the fields (accept the person selection fields) and then added the missing fields. Here is where things stopped working (even though not adding the people fields seems to be an issue as they should have been since my forms/views all include them). When I select a person field it shows me Item 1, Item 2, etc. I went into the settings of the field to confirm it set to Full Name and it is. Went back into play and then nothing shows up. Closed the app, came back in and the same issue, blank search field with no options even though I changed nothing and only viewed how it was setup. Didn't even unlock the field.
Now I added a new style form, and the people field shows #,#,# as my list of options to select. Again, checked to see how the field is set and moved Full Name to the top. Played the app and now I see the list of people, however, it seems to be limited to the first couple of hundred people (doesn't get past the As). If I search for a name that begins with anything other than A, nothing is displayed.
I also tried using the Entra table instead of the User table, and I have the same issues. Is there a trick to getting these people lookup fields working within canvas apps?
While that is my primary question, I should also add that the date fields function strangely. In dataverse, I set date fields to date only but when I add the form it includes time and doesn't submit updates. I tried adjusting the cards but the canvas app seems to believe time is necessary to submit to dataverse so removing time didn't resolve the issue. When I went back into dataverse and changed the dates to date and time the form started working. So, I guess I fixed it, but I would have though the form would just work with date only.
Last question I have is regarding dataverse attachment fields. When I created the table, I checked the box for attachments. Didn't do anything else (for examples, I didn't add a file field) and when I added the form control within Power Apps, I selected the attachment field which works flawlessly for multiple attachments. However, I can't find that field within the table. If I wanted to add/edit those attachments within dataverse, how do I access it?
I'd like to leverage a model driven and canvas app as part of this build, so I need to find a solution that works for both approaches.
Thanks!
Solved! Go to Solution.
I found a strange workaround for this situation. I often use the calendar control from the Microsoft Teams Power App environment as it provides some improved functionality over the standard Power App environment. I built a test app in the Teams environment and created the same User and Entra linked fields. I assumed the Teams environment controls wouldn't have the 500 row limit, and was correct. When I replaced the classic data card combo box with the Teams variant, everything started working. I can search and save without issues now! I hope this helps someone else with that same issue.
You've got a pile of questions in here, but I'll try to tackle the ones that I think are hanging you up:
First, the dates. A Dataverse date only column doesn't require time and instead will treat the date as though it always occurs at midnight. Make sure the Update property of that form card provides a valid date and not simply a string that looks like a date. If in doubt, use the DateValue() function to make sure it is providing a valid date.
For a related (lookup) column, make sure the Update property of its card is providing a valid record reference. This may mean using the LookUp() function on the Users table to identify the User with the matching email address, for example.
As you've noticed with your combobox on the User field, there are always a bunch of extra users with unusual names frequently starting with #. These are system-generated or added service principals in the environment and you'll likely want to filter those out of your combobox choices so users don't need to choose from them. On the topic of the Users table itself, only in the Default environment will all tenant users be included in the list. In other environments, users must be deliberately added and given a security role, which the Power Apps service does upon sharing an app with them. If you're using environments other than Default (and you should be doing this) and wondering where are all your users, that's what is happening. You can manually add users to the environment in the Power Platform Admin Center and then they will appear in the Users table.
That's a start, and it may be helpful to you and others to break this into separate posts for the forum.
Hope that helps,
Bryan
I think the question I have is whether people in a normal tenant (not GCC) observe that things just work when using forms within canvas apps? With a SharePoint list inside of a canvas app, adding a form just works for all SharePoint fields without out any edits.
The problem I'm running into with the User/Microsoft Entra ID table appears to be similiar to a delegation issue in that only the first 500 people are viewable. The environment has been shared across my organization and all users are visible within the dataverse table when adding records. It's only within the forms of Power Apps that searching is limited to the first 500 entires. For the classic form, it also just doesn't appear to work for those fields and appears this way:
Adjusting the User one makes it blank like the Entra one. Within the modern form, after a small adjustment of what is displayed, they are searchable up to the first 500 entries.
I hope that helps explain the issue a little better.
The 500 row delegation limit is a known limitation of the modern control set. For that reason, I frequently use the classic combobox, which can search/handle more than 500 rows.
Please make sure the security role you will be assigning to your users has appropriate permissions on the Users and your new table. To use the form control, they need to have permission to read the Users table at an org level, which sounds like it is configured. In addition, the security role will need read/write/update access at at least the user level on the new table. This can be configured through the Power Platform Admin Center.
As for the useability of a form control with Dataverse tables immediately after creation - In my experience, it will function, but it may not be the desired function for your use case. Modifying the form properties to achieve a set of business rules or desired user experience is a common thing to do.
Bryan
I wasn't aware of the 500 limit on the modern controls. I normally don't use those as I don't like the limits on configuration options. I only use them to test as sometimes they work differently than the classic form. Everything is configured correctly for the environment. For now though, its really just me testing things so it isn't a concern right now whether it will work for others.
It sounds like my issue might just be how the tenant/environment are configured for use with dataverse. Whether a modern form or classic form, neither works correctly once linked to a dataverse table that leverages a Lookup field to the User or Entra table. No matter how many times I adjust the classic forms data cards, I can't display the list of users. It will display the selection made within dataverse, so at least that is working. Unless someone has a suggestion, I think I'm heading back to SharePoint data sources.
I found a strange workaround for this situation. I often use the calendar control from the Microsoft Teams Power App environment as it provides some improved functionality over the standard Power App environment. I built a test app in the Teams environment and created the same User and Entra linked fields. I assumed the Teams environment controls wouldn't have the 500 row limit, and was correct. When I replaced the classic data card combo box with the Teams variant, everything started working. I can search and save without issues now! I hope this helps someone else with that same issue.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages