How to save, open and close a project file, and how to refresh it when the database has changed since you read it.
The project menu
New — start again with a new schema.
Open — load a .erproj.json file from your machine.
Save — download your project as a .erproj.json file.
Close — clear the project from the session.
Refresh — read the database again and bring your project up to date.
While a read, open or save is running, the menu is disabled and an overlay covers the page.
A large schema takes a few seconds.
Saving and opening
Each save downloads a new file, stamped with the date and time — for example
Sales-20260821-142530.erproj.json. Existing files are not overwritten.
The file holds the schema as you read it, your edits, and the server and database names. It
holds no password, user name or connection string, so it is safe to commit. There is no
Delete: remove a project by deleting the file yourself.
Your project is stored on your machine only. Nothing is kept on our side.
Refreshing
Select Refresh. You are asked for the database credentials again, or for
a freshly extracted DACPAC file.
A list of everything that has changed in the database since you read it is shown.
Select Apply to bring those changes into your project, or cancel to leave
it as it was.
When you apply a refresh:
Objects you have not edited are updated to match the database.
Objects you have edited keep your version and are listed as conflicts for you to
settle.
Objects deleted in the database are removed from your project, unless you had edited
them.
Objects you deleted stay deleted, unless the database changed them too.
Refresh after running a migration script to bring your project in line with the database and
clear the pending change count.