15 articles about Views, in reading order.
Start here
A step-by-step walkthrough, from an empty solution to a working app. Create a table, add five kinds of field, build a filtered view, and open it with real rows in about ten minutes.
Tables and data
Choose one field as a table's record image and one as its secondary text, and every list and lookup shows a picture and a second line beside each record's name. Two contacts with the same name stop looking the same.
Tables and data
A table whose records have a parent of their own kind can be shown as a tree, with another table's records hanging underneath, the selected record's form beside it, and a check that stops a branch being moved inside itself.
Model-driven apps
A field's type decides what it stores. Its control decides how people fill it in. Turn a yes-or-no field into a switch with its own words, show a date in the Persian calendar, and put a control you built yourself on a form.
Model-driven apps
A view is a list of a table's records, and it's where most people spend their day. Choose its columns, put them in order, give a column a width, and decide which list an app opens on.
Model-driven apps
Each column of a view can have its own header, date format, alignment and control, without changing the field. Turn "Purchase Date" into "Bought", write dates out in full, line up the amounts, and show a yes-or-no column as switches.
Model-driven apps
Build a filter from conditions in groups, each group either And or Or, and put one group inside another. Use it once while you browse a list, or save it on a view so everyone who opens the view gets it.
Model-driven apps
Two small views decide how people pick a record in a lookup. A lookup view chooses the columns of the Advanced lookup grid, and a quick find view chooses which columns typing searches, so "Berlin" finds the contacts in Berlin.
Model-driven apps
Any table with a date can be read as a calendar. Pick which field says when a record starts, colour the blocks by a choice, and people click an empty slot to book it, with the rooms side by side on the day sheet.
Model-driven apps
A command bar can use your organisation's words and follow the order people work in. Rename the platform's own commands, hide the ones a list doesn't need, drag everything into place, and divide it into groups.
Model-driven apps
Every table keeps four stamps for you, Created On, Created By, Modified On and Modified By, plus an Owner. Put them in a view or on a form and people see names and dates, not ids, with nothing to set up.
Model-driven apps
Every Parsware environment comes with an Organisation app. It holds your units as a chart, the people in each one, and who does which kind of work where, which is what processes route work by and what "my unit and below" access is measured against.
Platform Shell
Most of a working day in a Parsware app is spent in a view, the list of one table's records. Sort by one column or several, search, build a filter with And and Or, select records, open one, save it, and delete what you no longer need.
Languages and appearance
Every date in Parsware can be shown in the Gregorian or the Persian (Jalali) calendar, and the choice is one setting, separate from the language. Pick Persian and a week sheet starts on Saturday in Mehr 1405, a grid prints 23 Mehr, and a date picker opens on a Jalali month, in an app that is otherwise still in English.
Power Apps
A Parsware report can read a Dataverse view instead of the whole table. The view decides which rows, in what order and with which columns, and it's something your makers already know how to build. Here's a report of urgent cases, filtered and sorted by a view.
