Pait Group Blog

Configuring the Layout of SharePoint Forms Part 2: Conditional Fields

Back in June, I wrote a blog about how you can make default SharePoint forms a bit more user friendly and aesthetically pleasing using “Configure Layout” feature. For me, this is one of those life hacks that became a regular activity in your day-to-day life. Every list I create gets a configured layout form and then I decide if it needs additional functionality, like conditional fields.

Conditional fields in this case are fields that we only show to the user when they’ve provided certain information already. For my example, I’m going to modify the Travel Request form I already formatted. I added a new column for “method of travel” and included two choices: driving and flying. If the user selects flying, then the flight information fields will become visible. If they select driving, then those flight information fields remain hidden. Let’s start.

Read more

JSON Column Formatting (Part 2)

OK, so if you haven't read JSON Column Formatting (Part 1), this entry will probably make less sense than it should. Take a minute and check that out before you go on with this blog post, and you will be much happier.

Read more

Configuring the Layout of SharePoint Forms

I love a good form, but I am not a fan of the default form on SharePoint online. It does the job, sure, but it leaves so much to be desired. Most of the time I customize it via Power Apps, but that requires licensing and some Power Platform experience, and time. Sometimes, I work with clients that just don’t have those things. Luckily for them, there is a pretty simple way to spruce up the default SharePoint form using some copy paste and find and replace magic.

Read more

Functional Flair: adding Pictures to a SharePoint List

The List you need to use this JSON formatting as-is

Read more

JSON Column Formatting (Part 1)

I am a grumpy information worker. I work with customers for weeks, sometimes months, hammering out an information architecture for their Office 365 assets. We sweat details of navigation, metadata, and security. Queries are honed, web parts are implemented. User testing goes great. Naysayers start nodding their heads and smiling. Test groups give us notes and we knock off the rough edges. Plans are made, final deadlines are set and in a final attempt to button up the project someone goes and shows an executive and the fateful question is asked.

Read more