Following issue is occurring:
Already tried some different solutions:
The only solution I currently see, is to have a display input and an internal (hidden) input but this makes the application way to heavy in the long-term
Thanks in advance for your help and/or ideas
Solved! Go to Solution.
Regardless which option you choose, there is going to be additional logic required. If you need the number in 2 different formats, one for display and one for calculations, you will have to store the full number somewhere. PowerApps doesn't allow you to create circular references, so trying to set the display of your label/text inputs by referencing other properties of the same control won't work.
Your options for saving this number are:
The original question stated: For the display form I need the number with only two decimals. You haven't indicated when and how these numbers are being patched to the various collections, however reading that leads me to believe that the numbers have already been patched to a collection at the time of display. If that is the case, you could add a column in the collection(s) solely for the purposes of referencing the number (It wouldn't get patched to any data source). It would need to be a distinct value that indicates exactly which number it is. When you patch your collection(s) you would patch the number reference for each number patched. Then your text inputs could have the default set to the text formula or the full number value conditionally:
Text(Value(LookUp(CollectionName, RefColumn = "RefID").NumberColumn),"[$-en-US]##.00")
Since labels typically display either 'hard coded' information or information from somewhere else, you should be able to use an If or a Switch to determine whether it displays the full number or the rounded number, since the original number would still be available for your calculations. If that doesn't work, then a variable can be set in the OnChange property of the associated control that the label is referencing. The variable can then be used in the label's text property. If this method isn't an option then you are left with variables and hidden controls.
For the text inputs, if using the collection value isn't an option, and labels (if necessary), you would need to use a 'hidden control'. Personally I would layer a label and the text input. Then set the value of the label to the rounded value and then manipulate the visible properties of both to determine when each one is displayed. If you are wanting to display all the rounded numbers at the same time as a 'display' once the fields are filled out, you could use a single global variable set to true or false. You would set it to true in the App OnStart or in a control (if you have one) that tells the form it's being edited. Once the form is submitted set the variable to false. Set the text input's visible property to varDisplay and for the label set the visible property to !varDisplay.
Otherwise you would need another condition to tell each control when it should be visible.
You mentioned that this is a form? I know you said it might make your app 'way too heavy' in the long run but if you are using a form, it may be your best option:
Use this text formula to display the rounded values.
Text(Value(15.50),"[$-en-US]##.00")
Thanks for your response but the issue is not situated in a form. We are talking about +- 100 basic calculations that could extend to +- 250 so this would be a really hard solution.
We are patching multiple SharePoint data sources at once and working with multiple collections already. To add another collection with all this information, updating all current logic would make it quite hard.
Please feel free to enlighten us or to propose another solution
Regardless which option you choose, there is going to be additional logic required. If you need the number in 2 different formats, one for display and one for calculations, you will have to store the full number somewhere. PowerApps doesn't allow you to create circular references, so trying to set the display of your label/text inputs by referencing other properties of the same control won't work.
Your options for saving this number are:
The original question stated: For the display form I need the number with only two decimals. You haven't indicated when and how these numbers are being patched to the various collections, however reading that leads me to believe that the numbers have already been patched to a collection at the time of display. If that is the case, you could add a column in the collection(s) solely for the purposes of referencing the number (It wouldn't get patched to any data source). It would need to be a distinct value that indicates exactly which number it is. When you patch your collection(s) you would patch the number reference for each number patched. Then your text inputs could have the default set to the text formula or the full number value conditionally:
Text(Value(LookUp(CollectionName, RefColumn = "RefID").NumberColumn),"[$-en-US]##.00")
Since labels typically display either 'hard coded' information or information from somewhere else, you should be able to use an If or a Switch to determine whether it displays the full number or the rounded number, since the original number would still be available for your calculations. If that doesn't work, then a variable can be set in the OnChange property of the associated control that the label is referencing. The variable can then be used in the label's text property. If this method isn't an option then you are left with variables and hidden controls.
For the text inputs, if using the collection value isn't an option, and labels (if necessary), you would need to use a 'hidden control'. Personally I would layer a label and the text input. Then set the value of the label to the rounded value and then manipulate the visible properties of both to determine when each one is displayed. If you are wanting to display all the rounded numbers at the same time as a 'display' once the fields are filled out, you could use a single global variable set to true or false. You would set it to true in the App OnStart or in a control (if you have one) that tells the form it's being edited. Once the form is submitted set the variable to false. Set the text input's visible property to varDisplay and for the label set the visible property to !varDisplay.
Otherwise you would need another condition to tell each control when it should be visible.
So, as JR-BejeweledOne mention You shoul store your data in somewhere, if you don't want to put number statically in every text label. Let's consider You will do it manually:
You can use formatting like this Text(4.333,"#.#") becomes 4.3
Otherwise, when You use dynamically input You can state your source in Text where 4.333 placed.
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