What is a change set?
A change set is Salesforce’s point-and-click way to move metadata — custom fields, Lightning pages, Custom Metadata records — from one org to a connected one, usually from a sandbox to production.
In Salesforce
An admin builds an outbound change set in the source org, adds components to it and uploads it to a connected org, where it arrives as an inbound change set to validate and deploy. A change set carries metadata, never data records, which is why apps that keep their settings as data need those records exported and loaded separately.
How Rowhouse handles it
Rowhouse grids are Custom Metadata, so they travel in a change set like any other configuration. Add the grid’s Grid Configuration and every record that points to it — columns, display rules, filters, actions and child tables — under Custom Metadata Type records, together. A child table also needs its child grid in the target org, and the Lightning page the grid sits on deploys like any other.
A tip from the Grid Guide
Start each record’s name with the grid’s name. The records of every grid share one list in Setup, so a common prefix keeps one grid’s records together and makes them easy to find when you add them to a change set. Number Sort Order in tens, so a column can go between two others later.
Related terms
Change set: questions
What do I include to move one grid?
The Grid Configuration and every record that names it: its Grid Columns, display rules, Grid Filters, Grid Actions and Grid Child Tables. If it has child tables, include the child grids too, and the Lightning page if it is new in the target org.
Can I use a deployment instead of a change set?
Yes. Grid records are ordinary Custom Metadata records, so any deployment that carries metadata, or a project kept in source control, carries them too.
Three things you can verify without asking us
Free. Not freemium, not a trial, not a tier.
Install it, assign the permission sets, build your first grid on the Grid Admin tab. Everything else is in the Grid Guide inside the app.