09-21-2020 07:52 PM - last edited on 09-23-2020 09:06 AM by Allen
Join in and learn how the Microsoft Design team behind Lists approached designing a new List app. You'll learn more about the problems, principles and approaches. In deep dives, you'll see how they designed simple, beautiful UX that helps people be productive every day, with a strong focus on accessibility and inclusion.
09-23-2020 03:54 AM
09-23-2020 05:47 AMSolution
09-23-2020 01:46 PM
@Rachel Davis true! @Chris Knight, You can find access to PowerApps in the form under the "Configure" icon. It's the two panes and pencil one. There's "Configure layout", which is the in app JSON editor, and what Rachel mentions is "Customize with PowerApps". That will take you to the PowerApps editor where you start off with the basic look and functions, but can add all kinds of customization. It's pretty powerful.
09-23-2020 03:47 PM
@Ben Truelove Thanks
09-23-2020 03:59 PM
That's unfortunate about your tenant.
No, the form will still open on the right in SharePoint and the Lists app.
You can open a list in Teams inside the Lists App. If you go to the Office app button (Waffle), it will appear in that menu. From there you should be able to add JSON, or use PowerApps to customize your form, depending on what release your tenant is on.
I hope this helps.
09-23-2020 04:24 PM
@Chris Knight - You don't want the form to open full screen. It used to do that back in the day and it was the most annoying thing ever because it meant you couldn't move from one item to another. Open form, close form, next item, open form, close form next item.
By having the form in the right pane, you can simply hop from one line item to the next with the pane open. Just click the LINE for the next item. Not the selection bubble or the title field, click the LINE. This way you can jump from one item to the next.
As for your list in Teams, simply open the SharePoint site in back of your Team, create/edit your list as usual, format your columns & views, etc. Then add the list to your Team by putting it in a tab in a channel with the SharePoint connector. I've been doing it that way for a couple years now. You don't need the list app for that.
Very little of the actual list functionality is new. Most of it already exists in SharePoint. It's nice to have a central hub for all my lists and I like the UI changes and some of the new templates. But other than the new rules, most of it already exists in SharePoint.
09-23-2020 05:03 PM
That's sound advice Rachel, the SharePoint link would get you to the list outside of Teams faster. I do like to use the Lists App, mainly because I like that it doesn't have the left nav and site header, but just all list.
As for full screen in Teams, you can get a wider, multicolumn format in SharePoint and the Lists app by adding body JSON. Here's a snippet to just make it wide and multicolumn. If you use the header JSON I have, you'll want to set the bottom border of it to "0" as there's a border set by the section.
Hopefully you can either edit JSON or use PowerApps in your tenant at some point.
09-24-2020 05:38 AM
@Chris Knight I think you have an education issue here rather than a technology issue. In my case, most people don't know they have the ability to move from one item to another with the pane open. Once I show them the reason WHY the form is locked to the right pane, They are thrilled with the new flexibility.
This means we no longer rely so heavily on quick edit which in turn means I no longer have to have list views that show EVERY field. Now I can have views that show only the most important fields for sorting/filtering which means we've drastically reduced all the L-R scrolling.
Yes, of course, I've had a few stakeholders decide that the wide-screen custom Power App is higher on their priorities than easily jumping from item to item. But those are exceptions and it's a conscious, informed choice.
09-24-2020 05:55 AM
@Ben Truelove On JSON vs Power Apps
I've been noodling about Power Apps vs the JSON solutions you've shown to customize a form.
As SharePoint lead, I need to build things that I can hand off to the content owner and have them maintain it afterwards. Power Apps is a big improvement over InfoPath, but there's definite barrier in the hand-off area as Power Apps can have a significant learning curve.
Can you help me understand when JSON might be a better choice than Power Apps? Where's the decision line where I choose one over the other?
P.S. My JSON skills are limited to copying something from GitHub, pasting in my own values and putzing/cursing until it works. So major coding in JSON would require actually learning JSON.
P.P.S Thanks for the session. Clearly it's given me alot to think about.
09-24-2020 06:48 AM
Yes, being a designer, I'm not the most adept at coding, especially JSON, with it's more difficult structures, though I've heard our team has made some of that simpler.
I would say use PowerApps when you want to do lots of customizations, such as conditional fields, background colors, custom stylings, and totally different layouts.
I would use JSON when you just want to make a modestly different header, or footer, make it multicolumn and wide, or add content sections.
I do get your dilemma, it's kind of a rock and a hard place. I can see what I can do for providing some different kinds of JSON and honestly it would be good to have a primer on how to use it and what fields to edit. Usually at some point though, we provide a UX for this sort of work, much like we did for column formatting, which started as JSON only.
09-28-2020 11:45 AM
@MelissaBathum How come I'm not able to access MS Lists through my tenant's O365 portal? I can only seem to get to this app through Teams...I would really like to start building rules around the lists I have created as I believe it will solve a business problem we've been having at my org for years. Please advise.