Build an Offline Telecom Site Register

Build an offline Dataverse register that syncs telecom assets.

Introduction

30 Second Summary

Remote telecom sites rarely have perfect connectivity. A dropped signal can leave field workers unsure whether their updates were saved.

In this project, you will build an offline telecom site register with Microsoft Power Apps and Microsoft Dataverse. Your model-driven app will keep related Site and Generator records available through a network outage.

What You'll Build

You can switch off Wi-Fi and keep recording generator details at a remote site.

By the end of this project, you'll have:

A searchable telecom register where Site records open their related Generator details.
An offline-first field workflow that queues disconnected changes for synchronization after the connection returns.
A Microsoft Excel workbook containing synchronized Generator records with their Site lookup values.
Secret Mission: Replace the broad default offline profile with a filtered profile that downloads only Active sites plus their related generators.

Are there any prerequisites?

You need a Windows device running Windows 10 version 17763.0 or later plus a Microsoft work account.

Your account needs production licensing, access to a Power Platform environment with Dataverse, plus Environment Maker, System Administrator, or System Customizer permissions.

Before We Start

Before the hands-on work begins, this is your chance to commit to a field-ready telecom register. Focus on who needs it and why their work must continue when connectivity disappears.

Set Up Power Apps and Verify Access

Offline testing depends on a maker environment that can store the register. It also depends on a native client that keeps working when connectivity disappears.

In this step, you will confirm that Microsoft Power Apps can reach a Microsoft Dataverse database with the required maker permissions.

You will also install Power Apps for Windows with your Microsoft work account. You will confirm the licensing required for production use.

In this step, get ready to:

Confirm access to a Power Platform environment with Dataverse.
Verify your maker permissions plus the licensing required for production use.
Install Power Apps for Windows with your Microsoft work account.

Confirm your Power Apps environment and access

A Microsoft Power Platform environment is the workspace that holds the Dataverse database. The maker areas provide a quick way to confirm that you selected the correct environment.

Open the Power Apps maker portal in your browser.
Sign in with your Microsoft work account.
Select the intended environment from the environment selector.
Select Tables from the left navigation.
Confirm that the table page is available in the selected environment.
Select Solutions from the left navigation.
Select Apps from the left navigation.

You should see Solutions, Tables, and Apps in the maker portal. Their availability confirms that the selected environment exposes the Dataverse maker features needed for this project.

Why Licensing Matters

Licensing checks can feel like a blocker. This check only confirms what your employer already provides before you build.

The free Power Apps Developer Plan supports building and testing in a non-production environment. Production users need Power Apps Premium or a pay-as-you-go alternative.

The United States list price for Power Apps Premium is $20.00 user/month, paid yearly. Your employer may already cover the required license.

✔️ Access and licensing are confirmed

Confirm that your account has Environment Maker, System Administrator, or System Customizer permissions.
Confirm that production users have licensing that covers model-driven Power Apps plus Dataverse.

Your environment has the access required to create the tables later. Your production licensing position is also clear.

ⓧ Maker access is missing

This request gives your Power Platform administrator the decisions needed for the project.

Please provide access to a Dataverse development environment. Please assign Environment Maker, System Administrator, or System Customizer permissions.

Please also confirm whether our production users have licensing that covers model-driven Power Apps plus Dataverse.

Send the request above to your Power Platform administrator.
Return to Power Apps after access is granted.
Repeat the maker-area check in the intended environment.

ⓧ Production licensing is unclear

Please confirm whether our production users have licensing that covers model-driven Power Apps plus Dataverse. Please identify whether the environment is limited to non-production development.

Send the request above to your Power Platform administrator.
Keep this project in a non-production environment until production licensing is confirmed.
Record the administrator's licensing confirmation for later sharing decisions.

That clears the browser-side gate. You can install the native client without carrying an access surprise into later steps.

Install Power Apps for Windows

Microsoft Store distributes the native Windows client. This client provides the disconnected experience you will test later.

Press the Windows key to open Search.
Type Microsoft Store and press Enter.
Enter Power Apps for Windows in the store search field.
Select the Power Apps for Windows result.
Install the app from its store listing.
Press the Windows key after the installation finishes.
Type Power Apps and press Enter to launch the client.
Select Sign in.

You should see the work-account sign-in screen. That visible screen confirms that Power Apps for Windows is installed and launching correctly.

Seeing Update Microsoft Edge?

The Windows client requires WebView2 Runtime version 99.0 or later. An older runtime can also cause the client to close unexpectedly.

Press the Windows key to open Search.
Type Windows Settings and press Enter.
Use the settings search box to locate the installed apps list.
Find WebView2 Runtime in that list.
Confirm that the installed version is 99.0 or later.
Retry Power Apps for Windows after the runtime requirement is met.

Need help with the Windows client?

Sign in and verify the app list

The same Microsoft work account links the browser maker workspace to the native client. A visible app list proves that the client can reach your organization's Power Apps tenant.

Select Sign in if the sign-in page is still open.
Enter your Microsoft work email address.
Select Next.
Enter your Microsoft work account password.
Select Sign in.

You should see the signed-in app list. The project app does not exist yet, so this check focuses on the list itself.

A non-production environment can be hidden from this list. The visibility setting makes development apps discoverable when they are added later.

Select More (...) in Power Apps for Windows.
Select Settings.
Turn on Show non-production apps.
Return to the app list.

Before the final check, do you expect the browser session and the Windows client to be connected to the same work account?

Switch back to Power Apps in your browser.
Confirm that the intended environment is selected.
Confirm that Solutions is available.
Confirm that Tables is available.
Confirm that Apps is available.
Return to Power Apps for Windows.
Confirm that the signed-in app list is visible.

You should see the intended environment in the browser. You should also see the app list in Power Apps for Windows.

That is the setup hurdle cleared. Both Power Apps surfaces are ready for the telecom register.

Your Access Checkpoint

Power Apps for Windows is installed on the Windows device. It is signed in with your Microsoft work account.

The selected Power Platform environment has a Dataverse database. Your account has Environment Maker, System Administrator, or System Customizer permissions.

Production licensing is confirmed where applicable.

Your environment and native client are ready. Next, you will model the Site and Generator records in Dataverse.

Model Sites and Generators in Dataverse

Your Microsoft Power Apps access is ready for the register's data model. Field workers need site details to stay consistent when several generators belong to one location.

You will model this as relational data in Microsoft Dataverse. A parent Site table stores each location once.

A child Generator table connects equipment to that location through a lookup. That relationship becomes the path an offline profile synchronizes later.

Why Dataverse for this register?

A flat spreadsheet repeats site details on every generator row. Repeated values become difficult to keep consistent.

Dataverse stores one Site row. A lookup connects each Generator row to that site.

The same tables supply the forms and views used by the app. They also support the offline profile you configure later.

In this step, get ready to:

Create an unmanaged solution for the telecom register.
Build an offline-ready Site table with operational details.
Build an offline-ready Generator table with a required Site relationship.

Create the unmanaged solution

A solution keeps the app's tables, forms, views, and later offline configuration together. Creating these components inside one unmanaged solution also keeps your development work editable.

Switch back to Microsoft Power Apps from the previous step.
Select Solutions in the left navigation.
Select New solution on the command bar.
Enter Telecom Site Register in Display Name.
Select your organization's existing publisher in Publisher.
Enter 1.0.0.0 in Version.
Select Save.

The new solution opens with an empty component list. This is the container for both tables and the app you build next.

Select Overview in the solution pane.
Confirm that Telecom Site Register is identified as an unmanaged solution.

Your solution is ready. Every table you create inside it now stays grouped with the telecom register.

Can't create the solution?

If Solutions is hidden, select More in the left navigation to find it.
If Save is unavailable, check that every required solution field has a value.
If no suitable publisher is available, ask your Power Platform administrator which publisher your organization uses.

Help me troubleshoot solution creation in Power Apps.

Build the Site table

The Site table is the parent in this data model. Its primary column gives every location a stable identity for searches and relationships.

Select New from inside the Telecom Site Register solution.
Select Table.
Select Set advanced properties.
Enter Site in Display name.
Set the Primary column to Site ID.
Turn on Can be taken offline under the advanced options.
Select Save.

You will see the new Site table in the solution. Its primary column is now Site ID.

Why does the primary column matter?

The primary column is the human-readable value shown when another table looks up a Site row. Using Site ID makes identifiers such as SITE-001 visible when a generator is linked.

Select Columns in the Site table designer.
Select New column.
Enter Site Name in Display Name.
Select Text under Data type.
Mark the Site Name column as required.
Select Done.

The Columns list now includes the required Site Name field. This prevents a Site row from being saved without a readable name.

Create Region as a Text column by repeating the New column workflow.
Create Location as a Text column by repeating the same workflow.
Select New column to start the Operational Status column.
Select Choice as its data type.
Add Active, Maintenance, and Decommissioned as the available values.
Select Done.
Select Save Table.

The Site table now lists all four custom columns. Operational Status accepts one of the three defined values.

Select Update forms and views in the Site table designer.
Choose Site Name, Region, Location, and Operational Status under Add these columns.
Select the generated forms as update targets.
Select the generated views as update targets.
Select Update.

The generated forms and views now include the Site columns. Field workers can use these fields when the table is added to the app.

Open the data view for the Site table.
Create a new Site row.
Enter SITE-001 in Site ID.
Enter SITE-001 in Site Name.
Save the Site row.

You will see SITE-001 in the Site data. The parent record is ready for the Generator lookup.

Can't save the Site table?

Check that Site Name uses the Text data type and is marked as required.
Check that the Operational Status choices use the three values shown above.
Confirm that SITE-001 has a value in both required fields before saving the row.

Help me troubleshoot my Site table.

Build the Generator table and sample records

The Generator table stores equipment-specific details. Its required Site lookup keeps every generator attached to an existing parent record.

Return to the Telecom Site Register solution.
Select New.
Select Table.
Select Set advanced properties.
Enter Generator in Display name.
Set the Primary column to Generator ID.
Turn on Can be taken offline under the advanced options.
Select Save.

The Generator table now appears beside Site in the solution. Its primary column is Generator ID.

Select Columns in the Generator table designer.
Create Manufacturer as a Text column.
Create Model as a Text column.
Create Capacity (kVA) as a Decimal Number column.

The Columns list now includes the manufacturer, model, and capacity fields. Capacity can store decimal values for equipment ratings.

Select New column.
Enter Fuel Level (%) in Display Name.
Select Whole Number under Data type.
Enter Expected values range from 0 through 100. in the column description.
Select Done.
Select Save Table.

Fuel Level (%) now stores whole numbers. Its description documents the intended range from 0 through 100.

Select New column.
Enter Site in Display Name.
Select Lookup under Data type.
Select the Site table as the related table.
Mark the Site lookup as required.
Select Done.
Select Save Table.

The Site lookup now appears in the Generator table. Dataverse has created the relationship from each Generator row to one Site row.

How does the relationship work?

The Generator table is the child side of the relationship. Each Generator row stores a reference to one Site row.

One Site can therefore have several related generators. Site details stay in the parent row instead of being copied into every equipment record.

Select Update forms and views in the Generator table designer.
Choose Manufacturer, Model, Capacity (kVA), Fuel Level (%), and Site under Add these columns.
Select the generated forms as update targets.
Select the generated views as update targets.
Select Update.

The generated Generator forms and views now include all five custom columns. The required Site lookup is available for data entry.

Before creating the sample generator, predict which existing record the required Site lookup should offer.
Open the data view for the Generator table.
Create a new Generator row.
Enter GEN-001 in Generator ID.
Select SITE-001 in the required Site lookup.
Save the Generator row.

You will see GEN-001 saved with SITE-001 in its Site lookup. The child record now points to the parent Site row.

Return to the Site table's data view.
Confirm that SITE-001 remains saved.
Return to the Generator table's data view.
Confirm that GEN-001 remains saved with SITE-001 in the Site lookup.

That's the data model working: both rows save successfully while the lookup preserves their relationship. Your register now has the structure required for app navigation and offline synchronization.

Can't link GEN-001 to SITE-001?

Confirm that the SITE-001 Site row was saved before creating the Generator row.
Check that the Generator column targets the Site table and uses the Lookup data type.
Check that the Site table's primary column is Site ID.

Help me troubleshoot the Site lookup.

Your Site-to-Generator data model is complete. Next, you will turn these related tables into a searchable model-driven telecom register.

Publish the Telecom Register

Your Site and Generator records now share a required lookup inside Microsoft Dataverse. That relationship keeps each generator attached to its parent site.

Field staff still need a working interface for browsing the register. A model-driven app in Microsoft Power Apps turns your tables into that interface.

In this step, get ready to:

Create a model-driven app named Telecom Site Register.
Publish pages for the Site and Generator tables.
Verify connected record access through the published app.

Create the model-driven app

The app belongs inside your existing solution. This keeps the interface beside the tables that power it.

In Power Apps, select Solutions from the left navigation.
Select the Telecom Site Register solution.
Select New from the solution command bar.
Select App from the menu.
Select Model-driven app.
Enter Telecom Site Register as the app name.
Select Create.

The modern app designer opens with the new app inside your solution. Good progress. Your register now has an interface shell ready for its table pages.

Why Use a Model-Driven App?

Model-driven apps use Dataverse table metadata to generate the interface. Their layouts adapt automatically to different screen sizes.

Existing relationships provide navigation between related records. A canvas app would require you to build those screens manually.

Can't Create the App?

Confirm that Power Apps still shows the Dataverse environment selected earlier.
Return to the Telecom Site Register unmanaged solution before trying again.
Ask your Power Platform administrator to confirm your maker permissions if the app option remains unavailable.

Use help me create a model-driven app in my existing Power Apps solution for guided troubleshooting. You can also ask the Microsoft Power Platform Community for environment-specific help.

Add the Site and Generator pages

Each table page gives field staff a place to browse its rows. The selected forms control which fields they can edit.

Select Add page in the app designer.
Select Dataverse table.
Select the Site table.
Select the Generator table.
Select Add.

You will see Site and Generator as separate pages in the app navigation preview.

What Should Each Page Expose?

The Site page needs its generated form plus views containing Site ID, Site Name, Region, Location, and Operational Status.
The Generator page needs its generated form plus views containing Generator ID, Manufacturer, Model, Capacity (kVA), Fuel Level (%), and Site.

Open the Site page's component selection.
Keep the generated Site form containing the required field-entry columns.
Keep the Site views that expose the register columns.
Open the Generator page's component selection.
Keep the generated Generator form containing the required field-entry columns.
Keep the Generator views that expose the register columns.
Select Save in the app designer.
Select Publish.

Power Apps confirms the publication after processing your changes. Your connected register is now available to run.

What Do Save and Publish Do?

Save preserves your latest designer changes. Publish makes those saved changes available when the app runs.

Missing a Page After Publishing?

Return to Add page if either table is missing from the navigation preview.
Confirm that both table pages appear before selecting Save again.
Select Publish after the save finishes.

Use help me troubleshoot missing Dataverse table pages in my model-driven app if the page still does not appear.

Run the connected register

The published app should now expose the relationship you created in Dataverse. This connected test proves that staff can move from a site to its generator record.

Run Telecom Site Register from the modern app designer while your device is connected.
Select Site from the app's left navigation.

Before you search, predict which Site record the grid will return.

Enter SITE-001 in the Site grid search.
Open the SITE-001 row from the search results.

You will see the existing Site record open with its saved field values.

Before you save an edit, predict whether the required Site lookup will keep the generator attached to SITE-001.

Use the Site record's relationship navigation to open its linked Generator list.
Select GEN-001 from the linked Generator list.
Change Fuel Level (%) to 100.
Confirm that the Site lookup still displays SITE-001.
Select Save on the Generator record.

You will see the Generator record save with GEN-001 still linked to SITE-001. The fuel level now displays 100.

That is the working register published. Field staff can now search the Site grid before moving through the relationship to edit its Generator record.

Can't Reach GEN-001?

Confirm that GEN-001 still has its required Site lookup set to SITE-001.
Confirm that the Generator table page remains included in the published app.
Publish the app again after correcting either configuration.

Use help me find a related Generator record from a Site in my model-driven app for focused help.

Your telecom register now works while connected. Next, you will test what happens when that connection disappears.

Test the Online-Only Limitation

Your published model-driven app can now browse related Site and Generator records while connected. The unresolved question is what happens at a telecom site when the network disappears.

Microsoft Dataverse remains the live data source for every read and write. No offline profile currently copies those rows to the device.

In this step, you will deliberately remove Wi-Fi in Power Apps for Windows. This test creates the baseline that offline-first sync must improve.

In this step, get ready to:

Confirm the connected sample records load.
Test record access after disabling Wi-Fi.
Restore Wi-Fi before the next configuration step.

Confirm the connected baseline

An online baseline separates an app problem from a connection problem. Loading both sample records proves the app relationship works before you disconnect.

Switch back to Power Apps for Windows from earlier.
Select Telecom Site Register from the signed-in app list.
Select the Site table page from the left navigation.
Enter SITE-001 in the Site grid search.
Open the SITE-001 row.
Use the Site record's related Generator list to open GEN-001.

You'll see SITE-001 load with its saved details. You'll also see GEN-001 with its Site lookup set to SITE-001.

That gives you a clean baseline. The connected register can read both sides of the relationship.

Test the app without Wi-Fi

Turning off Wi-Fi is safe for this test. Your saved sample rows remain in Dataverse.

Before you disconnect, predict whether the same record actions can work without the live connection.

Select the network icon on the right side of the Windows taskbar.
Turn Wi-Fi off.
Return to Telecom Site Register.
Select the Site table page.
Attempt to open SITE-001 from the grid.

The record fails to open or stops loading reliably. The request cannot reach Dataverse without the network connection.

Use the create-record control on the Site grid's command bar if the grid remains available.
Enter SITE-NETWORK-TEST in the Site ID field if the form opens.
Enter Offline Network Test in the Site Name field.
Select Save.

The new row does not save to Dataverse. This is the intended shortfall in the current app.

Capture a screenshot of the failed open or save attempt with your usual Windows screenshot tool.

Why Did the Register Fail?

Offline mode has not been set up. The app has no local profile data to use during network loss.

An offline-first app stores selected rows on the device. It queues disconnected writes until the connection returns.

Restore the connected state

The next configuration step needs a working connection. Clear the unsaved test row before reconnecting so it cannot become part of the register.

Use the form's close control if the unsaved test row remains visible.
Discard the draft if a confirmation prompt appears.
Select the network icon on the right side of the Windows taskbar.
Turn Wi-Fi on.
Wait briefly for the network connection to settle.

Before you check again, predict whether the original sample records will load after the connection returns.

Return to the Site table page.
Enter SITE-001 in the Site grid search.
Open the SITE-001 row.
Use the related Generator list to open GEN-001.

You'll see both original records load again. This confirms that the app has reconnected without creating the unsaved test row.

Still Unable to Load the Records?

Confirm the taskbar Wi-Fi control shows an active network connection.
Wait briefly for the app to reconnect.
Return to the Site grid to search for SITE-001 again.

Need help restoring the register's connection?

You now have direct evidence of the online-only limitation. Next, you'll give the register local data access so field work can continue through network loss.

Enable Offline Sync and Export Records

Your model-driven app works while connected. The previous test showed that field work stops when its live connection disappears.

An offline profile copies the required Microsoft Dataverse rows to your device.

Power Apps for Windows stores disconnected edits as queued writes. When connectivity returns, the app synchronizes those writes automatically.

The synchronized records can then move into Microsoft Excel for verification.

In this step, get ready to:

Enable offline use with an automatically generated Default profile.
Create a Site with its related Generator while Wi-Fi is off.
Verify the synchronized Generator records in Microsoft Excel.

Enable offline use with a default profile

The automatically generated Default profile uses the tables already included in your app. It gives the Windows client the data required for local work.

How does the default profile help?

The Default profile is generated from the current app data. This provides a direct path to your first offline test.

The profile controls which Dataverse rows are downloaded to the device. Those local rows keep the register usable during network loss.

Switch back to the Microsoft Power Apps browser tab from earlier.
Select Solutions in the left navigation.
Open the Telecom Site Register solution.
Select Apps inside the solution.
Select the Telecom Site Register app.
Open More (...) for the selected app.
Select Edit.

The modern app designer loads with the existing Site and Generator pages.

Select Settings in the app designer.
Select the General tab.
Set Can be used offline to On.
Choose Default for offline access.
Select New profile with current app data.
Close Settings.
Select Save.
Select Publish.

You'll see publishing finish without an error. The published app now uses its automatically generated Default offline profile.

Offline setting missing?

Confirm the Site table still has Can be taken offline enabled.
Confirm the Generator table still has Can be taken offline enabled.
Confirm your account still has Environment Maker, System Administrator, or System Customizer permissions.

Help me troubleshoot the offline setting. You can also ask the Power Platform Community.

Create related records without Wi-Fi

The first connected launch downloads the app data covered by the profile. This initial synchronization prepares the Site and Generator tables for disconnected use.

Return to Power Apps for Windows from earlier.
Return to the Telecom Site Register app.
Keep the app active until the initial offline synchronization completes.

The initial sync has the most data to copy, so a short wait here is expected. You'll see a notification showing the number of downloaded rows and the disk space used.

Before you check the status, what do you expect the app to report when its offline data is ready?

Select the offline sync globe in the app navigation.
Check Device Status for Available.

You should see Available as the Sync status. Good progress. Your register now has a synchronized local dataset for offline work.

This second Wi-Fi test is controlled. You restore connectivity after saving two test records.

Before you disconnect, do you think the app can preserve a new relationship between records without contacting Dataverse?

Turn off Wi-Fi on your Windows device.
Return to the Site grid in Telecom Site Register.
Start a new Site record from the Site grid.
Enter SITE-OFFLINE-001 in the Site ID field.
Enter Offline Test Site in the Site Name field.
Save the Site record.

You'll see the Site record save locally while Wi-Fi remains off. This confirms the app can accept disconnected writes.

Switch to the Generator grid.
Start a new Generator record from the Generator grid.
Enter GEN-OFFLINE-001 in the Generator ID field.
Set the required Site lookup to SITE-OFFLINE-001.
Save the Generator record.

You'll see GEN-OFFLINE-001 remain linked to SITE-OFFLINE-001 while the device is disconnected. The app has preserved both rows in its local queue.

Offline record not saving?

Confirm the Site record has a value in the required Site Name field.
Confirm SITE-OFFLINE-001 appears in the Site lookup before saving the Generator.
Return to the offline sync globe if the app does not appear ready for disconnected work.

Help me troubleshoot an offline record that will not save.

Export synchronized records to Excel

Restoring connectivity lets the local queue send both records to Dataverse. The Generator record keeps its Site lookup during synchronization.

Turn Wi-Fi back on.
Keep Telecom Site Register active until its pending changes clear.
Select the offline sync globe.
Check Device Status for Available.

You'll see Available after the queued changes synchronize. That's the core offline workflow proven. Your disconnected Site and Generator records now exist in Dataverse.

Return to the connected Telecom Site Register in your browser from earlier.
Select the Generator table in the left navigation.

Before you export, do you expect the workbook to contain the record created without Wi-Fi?

Select Export to Excel on the command bar.
Select the downloaded workbook from your browser's download list to open it in Microsoft Excel.

Microsoft Excel opens the downloaded Generator data. Lookup values appear as text in the workbook.

Locate the row containing GEN-OFFLINE-001.
Confirm its Site lookup contains SITE-OFFLINE-001.

You'll see GEN-OFFLINE-001 with the SITE-OFFLINE-001 lookup value. This proves the offline relationship survived local creation and synchronization.

Offline row missing from Excel?

Return to Power Apps for Windows if the exported row is missing.
Keep Telecom Site Register active until Device Status shows Available.
Export the Generator table again after synchronization finishes.
Confirm the source Generator record still shows SITE-OFFLINE-001 if the exported lookup is blank.

Help me troubleshoot a synchronized record missing from Excel.

Your telecom register now works through a network outage. You have also verified its synchronized relationship data in Excel.

Secret mission

Limit Offline Data to Active Sites

Your default profile proves that offline synchronization works, but it can carry more rows than a field worker needs. Replace it with a relationship-aware profile that keeps Active sites and their generators available while leaving Decommissioned sites off the device.

Clean Up Your Resources

Your app resources stay in Microsoft Dataverse until a maker or administrator removes them. Keeping them can continue to consume licensed access plus Dataverse storage.

Decide whether to keep your resources running, pause them to come back later, or delete them entirely.

Cost warning

Dataverse plus production model-driven app use can require paid licensing. Microsoft Power Apps Premium is currently listed at $20.00 user/month, paid yearly, in the United States.

The free Developer Plan supports building plus testing in a non-production environment. Production users need Power Apps Premium or a pay-as-you-go alternative.

Resources you used:

Published Telecom Site Register model-driven app in the selected Dataverse environment.
Matching site map for the Telecom Site Register app.
Custom Generator table containing sample records plus synchronized offline records.
Custom Site table containing sample records plus synchronized offline records.
Unmanaged Telecom Site Register solution container.

Keep everything running

No action needed. Choose this if field testing or development is continuing.

Keep the Telecom Site Register app published.
Leave Can be used offline enabled.
Retain the Active Telecom Sites Offline profile assignment.
Retain the Default offline profile for future comparison.
Keep Power Apps for Windows signed in for more disconnected testing.
Confirm production licensing before sharing the app with field workers.

Pause - I'll come back to this later

This option hides the app from common discovery while preserving its configuration. Your tables plus records remain available for later work.

Return to the Telecom Site Register solution in Microsoft Power Apps.
Select the Telecom Site Register app.
Select More (...).
Select Turn off.

You should see the app status change to Off. The app disappears from common discovery.

Direct links continue to work.

Ask a Power Platform administrator to remove the app's assigned security-role access for a strict pause.

The app remains intact. Its Dataverse data plus offline profiles also remain in the environment.

Delete - I don't want to use this again

Permanent deletion can feel drastic. Your verified Excel workbook remains separate from these Dataverse deletions.

The Generator table is the child side of the relationship. Removing it before Site clears the required lookup dependency.

Return to the Telecom Site Register solution in Microsoft Power Apps.
Select the Telecom Site Register model-driven app.
Select Delete.
Choose Delete from this environment.
Select the app's matching site map.
Select Remove.

The app entry plus its matching site map are now removed from the environment.

Select the Generator table in the solution.
Select Remove.
Choose Delete from this environment.

The child table is now gone. Its sample records plus synchronized offline records are permanently deleted.

Select the Site table in the solution.
Select Remove.
Choose Delete from this environment.

Your Site records are now removed from Dataverse. This includes the synchronized offline Site records.

The unmanaged solution is a grouping container. Deleting that container alone would leave its unmanaged components plus associated data in the environment.

Return to Solutions.
Select the Telecom Site Register solution.
Select Delete.
Return to Solutions after deletion finishes.

You should no longer see the Telecom Site Register solution. The app plus its custom tables are no longer available in the environment.

Nice Work!

You did it! You built a telecom asset register that protects related Site and Generator records when connectivity disappears.

You've learned how to:

Build a relational Site-to-Generator data model in Microsoft Dataverse that preserves each generator's link to its parent site.
Publish the Telecom Site Register as a model-driven app for field work during connected or disconnected use.
Verify offline-first synchronization in Power Apps for Windows after reconnecting. Export synchronized Generator records with their Site lookup values to Microsoft Excel.
Secret Mission: Replace the broad default profile with the Active Telecom Sites Offline profile. Disconnected searches now include Active sites with their related generators while excluding Decommissioned sites.

Ready to quiz yourself?