cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

DisplayMode=View removes border

Would be greating if having controls with DisplayMode=View can have a border. I see a similair post about the padding being removed when in View mode, but since this is a seperate issue, I'm making a new item.

 

Any way to have a control (textbox or label) have a border, and also be in View Mode?

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

@v-yamao-msft and @cherie what Dave is saying is when a control property is set to DisplayMode.View it does not have a border. If you try this out by placing a control and changing it's DisplayMode to View you'll notice the border settings can be set to show but when changed to "View" the border doesn't appear.

 

@dave-jorgensen I can't find any way to make a .View control have a border, maybe there is an actual way to do it but if not my suggestion would be to put this on the ideas forum to see if it gains any traction and can be added to the PowerApps future updates.

 

You can post ideas here: https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

 

Edit: I just tried the old school method of putting a rectangle behind a text input box and it doesn't look too bad and works similar to a  "border" would. Maybe a temporary method of getting what you want? All I did was add a rectangle icon from the Icons menu, then sent it to back from the Reorder menu in Home. Then it was just tweaking it to create a border behind the .View set text input box.

 

fakeborder.PNG

View solution in original post

47 REPLIES 47
cherie
Power Apps
Power Apps

Hey,

 

If you set the border for a label or a text box, it should show up.

 

You can set it in the properties pane at the side

 

border.PNG

v-yamao-msft
Community Support
Community Support

Hi dave-jorgensen,

 

With the Label control being selected, you may try to change the following properties about Border to modify its border.

3.PNG

 

More details about Border properties please check it at here:
https://powerapps.microsoft.com/en-us/tutorials/properties-color-border/


Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-yamao-msft and @cherie what Dave is saying is when a control property is set to DisplayMode.View it does not have a border. If you try this out by placing a control and changing it's DisplayMode to View you'll notice the border settings can be set to show but when changed to "View" the border doesn't appear.

 

@dave-jorgensen I can't find any way to make a .View control have a border, maybe there is an actual way to do it but if not my suggestion would be to put this on the ideas forum to see if it gains any traction and can be added to the PowerApps future updates.

 

You can post ideas here: https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

 

Edit: I just tried the old school method of putting a rectangle behind a text input box and it doesn't look too bad and works similar to a  "border" would. Maybe a temporary method of getting what you want? All I did was add a rectangle icon from the Icons menu, then sent it to back from the Reorder menu in Home. Then it was just tweaking it to create a border behind the .View set text input box.

 

fakeborder.PNG

Thanks - not a bad hack, but not all that practical once you have a significant number of textboxes. 

I won't be marking as answer, because it doesn't solve the issue - the fact that view displaymode doesn't allow borders, but once again - thanks for suggestion.

Not sure if that helps you, but I solved that in this way:

 

  1. New Forms/Edit
  2. Add datacard with TextInput
  3. Set TextInput DisplayMode=DisplayMode.Edit

You can keep DisplayMode.Edit all the time and switch from View to Edit on Form level. In FormMode.View mode the TextField have the border and value is read only even with the DisplayMode.Edit used.

To enable editing you just need to switch form to FormMode.Edit

You can change the control to View and the Datacard to Edit, then your border will display on the datacard.  Not sure if that helps

motami
Advocate I
Advocate I

I was having this same problem, no borders when in view mode but I found a workaround, at least for me.

 

I had my Form Displaymode set to View and all my dropdown control boxes all set to "Parent.DisplayMode".

I changed the dropdown control boxes to "DisplayMode.Disabled" and they appear exactly like in View mode but you can set/change/add border.

 

Examples in the screenshots.

 

Form = "DisplayMode.View"; Dropdown boxes = "Parent.DisplayMode"Form = "DisplayMode.View"; Dropdown boxes = "Parent.DisplayMode"

                             

Form = DisplayMode.View ; Dropdown boxes = DisplayMode.DisabledForm = DisplayMode.View ; Dropdown boxes = DisplayMode.Disabled

 And then you can change the borders however you like.

 

Hope it helps.

 

Miguel

 

PS: Sorry for unearthing this old post, I found it while searching for a solution to my problem.

 

 

Anonymous
Not applicable

@motami Thanks for revisting and posting useful info. You don't owe anyone an apology. Microsoft on the other hand...

 

IMHO the fact that as of October 2018 this is STILL the case is absurd. To my mind this example is 100% emblematic of a number of just completely inane shortcomings of PowerApps...that such complex workarounds are required for such a SIMPLE objective.

This behaviour is by design.  

 

The logic behind it is that when the control is in edit mode it shows the actual input control and allows user to input content and make selections.  When it is in view mode, it just shows the data in a more presentable way, in a way that makes it obvious to the end user that the data is just being displayed and cannot be changed.  For the text input control this eliminating borders as those are the main markers of the input controls.  For other controls (like date picker, combo box, dropdown) it elminates the borders and all other elements of an input control.

 

I am curious to find out what problems is this causing in your app designs, perhaps the change is too drastic, but perhaps the solution lies elsewhere.

- not filipk@microsoft.com, please private message me if you can't share with everyone

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

Users online (1,756)