cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
tagustin2020
Power Participant
Power Participant

Conditional Formatting for LookUp Labels

Hello, I am working on a new request form (screenshot attached). I have it set up so that when the user selects a Project Number from the dropdown control, the Project Name and Program Mgr/Product Engr labels are automatically populated via LookUp formulas. I kept the underlying text input controls in the data cards so the selections could be written back to my SharePoint list.

 

The current Text formula for the Project Name label is:

LookUp('Project List','Project Number' = ddProjectNumber.Selected.'Project Number','Project Name')

 

The current Text formula for the Program Mgr/Product Engineer label is:

LookUp('Project List','Project Number' = ddProjectNumber.Selected.'Project Number','Project Owner'.DisplayName)

 

When the user first launches the form, I would like the Project Name and Program Mgr/Product Engr labels to be disabled and read “Auto-populates based on Project Number selection”. Once the user has selected something from the Project Number dropdown control, that message should be replaced with the results of the LookUp and the label should be read-only as they don't want them to allow them to edit the results. I tried a If(IsBlank type formula, but didn’t get very far since I am still new at this. Can you please help me develop the correct syntax? Let me know if you need any additional information.

 

The other thing I should mention is that the new request form is on a dedicated screen of its own. When the user selects an item from the gallery to view or edit, they are taken to a separate screen with multiple tabs. Do I still need to include some type of If(frmNewRequest.Mode = FormMode.New, FORMULA, Parent.Default) type syntax in all of my new request form fields? If so, can you help me incorporate that piece into the LookUp labels as well? Thanks in advance for your kind assistance. Teresa

1 ACCEPTED SOLUTION

Accepted Solutions
faustocapellanj
Memorable Member
Memorable Member

Hello @tagustin2020 

This is how I would approach your scenario. On your drop-down OnChange property, enter a formula similar to this one: Set(varProjectInfo, LookUp(ProjectList, 'Project Number' = ddProjectNumber.Selected.'Project Number'). Once that's done, set the Text property of your Project Name label to varProjectInfo.'Project Name', and then set the Text property of your Program Mgr/Product Engineer label to varProjectInfo.'Project Owner'.DisplayName

The reason for this approach is that the LookUp is pulling the entire record and the varProjectInfo variable will have all the columns available for use, i.e. varProjectInfo.'Project Name' and so on and so forth. Also, this will decrease the number of LookUp calls the form will execute, which prevents performance issues when having too many lookups.

As for the other part of the app where the user selects a record from the gallery, don't use galleryname.Selected. Instead, if you are using a button to select the gallery item or you want to do it directly in the gallery's OnSelect property, set another variable similar to this code: Set(varRecord, ThisItem), then in the form's Item property, set its value to the varRecord variable.

Please try these approaches and let me know.

Regards,

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

View solution in original post

13 REPLIES 13
faustocapellanj
Memorable Member
Memorable Member

Hello @tagustin2020 

This is how I would approach your scenario. On your drop-down OnChange property, enter a formula similar to this one: Set(varProjectInfo, LookUp(ProjectList, 'Project Number' = ddProjectNumber.Selected.'Project Number'). Once that's done, set the Text property of your Project Name label to varProjectInfo.'Project Name', and then set the Text property of your Program Mgr/Product Engineer label to varProjectInfo.'Project Owner'.DisplayName

The reason for this approach is that the LookUp is pulling the entire record and the varProjectInfo variable will have all the columns available for use, i.e. varProjectInfo.'Project Name' and so on and so forth. Also, this will decrease the number of LookUp calls the form will execute, which prevents performance issues when having too many lookups.

As for the other part of the app where the user selects a record from the gallery, don't use galleryname.Selected. Instead, if you are using a button to select the gallery item or you want to do it directly in the gallery's OnSelect property, set another variable similar to this code: Set(varRecord, ThisItem), then in the form's Item property, set its value to the varRecord variable.

Please try these approaches and let me know.

Regards,

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

Hello Fausto,

 

Thank you for the advice. I'm excited to try it. Our IT Dept is working on my computer so I may not have a chance to try this until tomorrow. I'll get back to you as soon as possible. Have a great weekend!

 

Kind regards,

Teresa

Hello Fausto,


Thanks again for responding to my inquiry. I entered the following formula into the OnChange property of my Project Number dropdown control which I named ddProjectNumber. Unfortunately, it is generating error messages. I notice that your formula is stated as ProjectList without spaces or apostrophes. Are you recommending that I create a Collection in the OnVisible of the New Screen form for the Project List? If so, seems like you would have entered a name of colProjectList, but I thought I should ask anyway. The Text property formulas aren't working either as intellisense is unable to find the list column names.

 

Here is how I have the OnChange property currently set. Notice the apostrophes and spaces in 'Project List'. I tried entering it as ProjectList, but it doesn't work that way either.


Set(varProjectInfo,LookUp('Project List','Project Number' = ddProjectNumber.Selected.'Project Number')


I’ve attached a screenshot of the errors I am getting.

 

While I welcome opportunities to make my app more performant, my original question was around how do I disable the two other fields until someone selects something from the dropdown. I don't want them to attempt entering information into those labels.

 

In regards to your second piece of advice, I am already doing that, but thank you, it is great advice. 

 

Kind regards,

Teresa

Hi Teresa, The ProjectList name in the formula was in reference to your formula, but I should've used the same name you have to avoid confusion. My apologies. When you execute the OnChange property of the drop-down, please to go to File > Variables and see if the varProjectInfo variable has a value in it. If it does, it should show you one record with multiple columns in it. These are the columns you can then use along with the variable as varProjectInfo.ColumnName. Can you please try that and let me know? Thank you!
Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

Hello Fausto,

 

Thanks for getting back to me. Since the On Change formula is throwing errors it isn't possible to execute it, nothing is happening. I checked the Variables and there is nothing registered at this point. Any suggestions of what I should try next?

 

Teresa

Hi Teresa,

Next thing I would try is to add a button and add the code to the button's OnSelect property. Then hard code an actual project number in the formula and see what that returns.

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

Thank you Fausto. Do you have any thoughts on how I can achieve my original inquiry? If not, I'll mark your latest suggestion as a solution and will start a new ticket since this thread is getting long. Have a great day! Teresa

Hi Teresa,

No need to start a new thread. Since the app checker says there's an error in the formula, can you look at what the error is directly in the formula and then post it here? That way we know what the app is complaining about and fix it.

Regards.

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

Hi Fausto,

 

I was able to set the variable this time. Turns out I was missing a parenthesis. I changed my Program Manager/Product Engineer to a people picker control and am not seeing an error when I enter varProjectInfo into the Default property of the data card, but I haven't been able to test it yet as I am still getting errors in the Project Name fields. The purpose of the text input field is to write the Project Name back to the SharePoint list. I tried doing this based off of just a label and was not successful.

 

First, I tried entering varProjectInfo into the Text property of the label. I got this error.

Expected Text Value.lblProjectName.Text

 

I then tried entering varProjectInfo into the Default property of the text input and got this error.

Expected Text Value.txtValueProjectName.Default

 

Teresa

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Top Solution Authors
Top Kudoed Authors
Users online (2,719)