cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
SA-KRP
Frequent Visitor

SharePoint Webpart & Forms Questions?

Not sure this is the right board, I can't find anything listed as SharePoint.

 

I am rebuilding a SharePoint 2013 site in SPO and have a several lists I used to display on the sites home page using multiple "list" webparts but cannot get the same results.

  1. Context Menu: List items displayed cannot be edited directly from the webpart, only showing "Share" or "Copy link". I have turned off the quick edit but even with that on the context menu is still limited, even to the Site Owner. (Left: SP2013, Right: SPO)
    SAKRP_1-1718989591366.png
    Also, I used to be able to add custom items to the context menu that would open a custom form eg "Assign QCR" (above image) which would open a custom Edit form (image below) for the QCR Admin (staff). Not sure with the current form limitations this is possible. This is the same list just a form with super limited fields displayed with most read-only, anyone can open the form but has to be done from the item context menu.
    SAKRP_0-1718997242585.png

     

  2. Webpart Views: With SP2013 the view was set on the webpart but in SPO a view for the webpart has to be selected from one of the existing List views. This is cluttering up the actual displayed "views" on the List. I have multiple pages with webparts that have specific views that I don't want visible for staff in the List's "views" menu.
    For now, I have just prefixed these views with a "z_" to push them down the list of views.
  3. Webpart of a Task List: When trying to add a "Tasks" list as a webpart, all task type lists are not available to select? 
  4. Forms and Field Display Type: In SP2013 I was able to edit the Open, Edit, Display forms to restrict select fields to Read-Only, eg on a New form a user could set "Field A's" value but in the Edit form it was only displayed (read-only) so it wasn't changed. In SPO the Open/Display forms a user can edit any field as well.

    I have used the SPO forms "Configure Layout" option to adjust the layout, but this appears to be a global change to all item forms. I can't find a way where the New and Edit forms display fields differently. I see the Header/Footer option, but this still doesn't solve the issue as many fields need to be available in the New form but not in the Edit as Flows run based on the original input.
    Is the only way to resolve by using the "Forms" or Power Apps?

    Here are the SP2013 forms New/Edit
    SAKRP_2-1718991659768.png

     

Any suggestions, direction to articles would be appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions

It looks like you’re on the right track! Let’s refine your formula for the DisplayMode property. You can use the following formula to achieve the desired behavior:

DisplayMode = If(
    varIsNew,
    DisplayMode.Edit,
    DisplayMode.View
)

This formula checks whether varIsNew is true. If it is, the DisplayMode will be set to Edit; otherwise, it will be set to View.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Sunil Pashikanti - Tech Blog

 

 

View solution in original post

7 REPLIES 7

Hi @SA-KRP,

 

Let’s address each of your SharePoint-related questions and explore potential solutions:

 

Context Menu and Custom Forms:
In SharePoint Online (SPO), the context menu behavior might differ from SharePoint 2013.
To achieve custom context menu actions (like “Assign QCR”), consider using Power Apps or custom forms.
Power Apps allows you to create custom forms with specific fields and actions, which can be triggered from the context menu or other UI elements.

 

Webpart Views:
In SPO, web parts are associated with existing list views.
To manage views more effectively, consider creating specific views for your web parts (e.g., “Staff View,” “Admin View”) and prefixing them as you’ve done.
You can also use audience targeting to control which views are visible to specific users or groups.


Webpart for Task Lists:
When adding a web part for a task list, ensure that the list is set up as a task list (with the appropriate content type).
If you’re still facing issues, consider creating a custom list with similar fields and using it as a workaround.


Forms and Field Display Type:
In SPO, customizing forms is more flexible using Power Apps or SharePoint Forms.
Power Apps allows you to create dynamic forms with conditional logic, read-only fields, and customized layouts.
For read-only fields in specific form views (e.g., New vs. Edit), Power Apps is a powerful solution.
You can create separate screens for New and Edit forms, controlling field visibility and behavior.


Global vs. Form-Specific Changes:
While the “Configure Layout” option affects all item forms globally, Power Apps allows you to create form-specific changes.
Use conditional visibility rules in Power Apps to show/hide fields based on form type (New/Edit).
Consider using header/footer options in Power Apps to enhance the form layout.


Power Apps or Forms:
Both Power Apps and SharePoint Forms (modern experience) offer solutions for customizing forms.
Power Apps provides more flexibility and control, especially for complex scenarios.
If your requirements go beyond what SharePoint Forms offer, Power Apps is the way to go.


Remember that Power Apps provides a rich environment for customizing forms, handling complex logic, and creating user-friendly experiences. Explore Power Apps further to build tailored solutions for your SharePoint lists.

 

References:

https://lightningtools.com/blog/forms-web-part/

SharePoint Online Microsoft Forms Web part - Enjoy SharePoint

 

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Sunil Pashikanti - Tech Blog: PowerApps

 

 

Thanks SunilPashikanti for the detailed response, I'll go through your comments and give it a try.

 

We have been using SharePoint On-prem for some time now (WSS3, SPF 2010, SPF2013) and I know what I want to do but SPO has many changes that are hard to find the "new" way to accomplish what we have in place. It feels like I am starting all over again with the step learning curve with SPO.

RE: 4 Forms and Field Display Type

After reading a few more articles I thought before I dive into learning PowerApps, I'd give it one more try using the native list/column tools, eg "Edit columns" w/conditional formula, "Configure Layout" and "Field Validation".

 

The thought was I'd use a conditional formula to expose/hide a field and use JSON in the Header to list said field once set.
Background: There are several columns that are auto populated by a PowerAutomate Flow and figured I could use one of them, eg NUL to Show, NOTNULL to Hide. It seems there isn't a way to use conditional formulas for this NUL/Empty check?

 

[Status] field (Type=Choice): (WORKING)

  1. to always hide I used conditional formula "=if(length([$Status]) == -1, 'true', 'false')"
  2. Then use JSON to show this in the Header only

[EngType] field (Type=Choice): (NOT WORKING)

  1. Set column settings "Required"=No
  2. Set column validation to "=IF(([Eng Type])="",FALSE,TRUE)"
  3. To Show/Hide - There is the Default [Title] (Type=Text, Default Value=Blank/Empty) column that has been renamed to "ClientName" I tried setting the formula to use that field. I have tried many variations and even other columns, eg [StartDate] (Type=Date, Default Value=Blank/Empty)
    1. =if(length([$Title]) <= 1, 'true', 'false')    (not working) maybe length() isn't valid in this case?
    2. =if([$StartDate] >= Date('1/1/1900'), 'true', 'false')    (not working)
    3. As a test "=if([$Status] == 'Signed-in', 'true', 'false')"    (works but is doesn't hide the column soon enough as this column is updated later in the process.)
    4. Many other variations I can't remember now.

 

No matter what I try or what other fields I reference I can't get the [EngType] to show/hide the way I want it to.

 

Goal, 

  • Show column/field [EngType] on a new item form
  • Hide [EngType] on existing items, eg when editing/viewing forms, and only display in the Header.

Note: I have confirmed I am using the columns system name by checking the URL "Field=" when editing the column.

 

Hi @SA-KRP

 

As of now I can see only one option, edit the SharePoint online form with PowerApps, this is not a new PowerApps application, but editing the existing SharePoint custom list form, hope it fits for your requirement.

SunilPashikanti_0-1719540876377.png

When you see the form in PowerApps, 

SunilPashikanti_2-1719541271227.png

Select the SharePointIntegration, 

Choose "OnEdit" in property dropdown

Write the below code in formula bar

Set(varIsNew, false);

Again Choose "OnNew" in property dropdwon

Write the below code in formula bar

Set(varIsNew, true);

SunilPashikanti_3-1719541500415.png

 

Now we got a variable that consists true value when a form is New, and false value when a form is Edit.

 

Now, select your text box field that should be hide/display, and select its visible property and add "varIsNew".

SunilPashikanti_5-1719541584515.png

 

If it does not allow you to edit, that means it is locked, you can unlock it from right side property window.

SunilPashikanti_4-1719541555985.png

 

Save and publish the app, 

SunilPashikanti_6-1719541622738.png

Now go back to your SharePoint list and clear the cache in the browser (Ctrl + F5) at least 3 to 5 times, it clears the cache from the browser.

If it works, then you will see the magic.

 

My New Form, showing Area field:

SunilPashikanti_7-1719541715367.png

My edit form, hiding Area field:

SunilPashikanti_8-1719541745844.png

Hope it helps!!!

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Sunil Pashikanti - Tech Blog: PowerApps

 

SunilPashikanti I am testing the option you suggested with Power Apps but I want to clarify a few things;

  1. Once Power Apps is turned on for the forms setting for the list, it is then an all or nothing step, meaning all forms must be managed via Power Apps for the list?
    Therefore, all default list forms will need to be recreated in Power Apps, New, Display, Edit.
  2. It is possible to have multiple forms via Power Apps, to edit the list items, eg or will there be one designated for that must use conditional formatting (or other feature) to show/hide columns based on the user in the correct edit/read-only status? eg
    1. New form
    2. Edit Form
    3. other Custom forms

All having varying columns displayed/hidden in Edit or Read-only status.

As in my SP 2013 solution there are multiple/different forms for specific audiences;

  • New
  • Display
  • Edit
  • Assign QAR (not restricted by permissions, just a deliberate action needed to open this form needed)
  • Assign Tax Reviewer (not restricted by permissions, just a deliberate action needed to open this form needed)

All accessible from the same context menu on item, the Assign QAR is drastically different from the typical New, Edit, Display forms but is form the same list. It essentially is a simplified form with only 2 editable fields. There is a similar Assign Tax Reviewer form with a few different columns.

 

SAKRP_0-1719938179520.png

 

I ask because the Power Apps seems to be more about editing the default form and taking different action depending if it's in OnEdit or OnDisplay modes. The forms I want are very different.

 

Additional Notes;

To be clear, on this one list I have approx 5 forms, all can be opened by all staff and not secured by user context, the reason for the different forms it to minimize changes to select columns and it takes a deliberate action by the staff to open the special forms from the context (eg Assign QAR).

  1. New, Edit, Display (must be available to all staff)
  2. Assign QAR (available to all staff, with limited columns as Editable)
  3. Assign Tax Reviewer (available to all staff, with limited columns as Editable)

The fact that all staff need to see any of these forms is a bit confusing in Power Apps how this is done based on the other posts I have read where the columns access is more dependent on the user.

I followed the instructions, and the Textbox I set the Visible=IsNew, the data is not displayed, so half way there.

What I want to see is the data displayed on the Edit BUT Read-only/Displayed.

 

I was trying to use the DisplayMode property with this formula but getting an error "function if has some invalid arguments".

If(varIsNew=true,Edit,View);

 

The 2nd attempt below seems to be working but wanted to confirm with you I am on the right track now? 

If(varIsNew=true,DisplayMode.Edit,DisplayMode.View)

It looks like you’re on the right track! Let’s refine your formula for the DisplayMode property. You can use the following formula to achieve the desired behavior:

DisplayMode = If(
    varIsNew,
    DisplayMode.Edit,
    DisplayMode.View
)

This formula checks whether varIsNew is true. If it is, the DisplayMode will be set to Edit; otherwise, it will be set to View.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Sunil Pashikanti - Tech Blog

 

 

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,275)