Add a Component to a Solution
How a maker adds a component to a solution, with the publisher prefix enforced.
How a maker adds a component to a solution, with the publisher prefix enforced.
How a maker adds a business process to a solution — naming it first, drawing it second — and what a process is for.
How a maker creates a publisher whose prefix namespaces solution components.
How a maker turns a designed template plus a query into a printable report that users can run from a record or a list.
How a maker creates a solution owned by a publisher.
How a maker adds an application file — JavaScript, CSS, HTML, an image or SVG — that is stored in the platform and packaged with the solution.
How a maker deletes a table from an environment, and why a delete can be blocked.
How a maker removes a solution — deleting an unmanaged one, or uninstalling a managed one — and what happens to the components in it.
How a maker exports a solution from an environment as a portable, versioned package.
How a maker decides what a role may do, inside the solution that ships it — and to which records.
How a tenant admin imports a solution package into a target environment to promote work between environments.
How a maker installs a Custom Control by uploading the package built from it, so it can be bound to a Model-Driven form field in an environment.
How a maker installs a Custom React App by uploading the package built from it, so the Platform Shell can load it in an environment.
How a maker saves a question once in a solution so charts, reports and dashboards can name it instead of each keeping their own copy.
How a maker makes a table's rows travel with the solution — a Seed Data view decides which rows and which columns, and an import upserts them.
The canonical, versioned schema for an exported Solution package used to promote work between environments.
How a maker declares a setting once in a solution and lets each environment answer it for itself.
How a maker writes a shared BS Lang helper once and imports it from business rules and commands.
How a maker writes markdown guides that travel with an app, show in its Help menu, and open from a screen or a command.