-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
98ec6c9
commit 3299aa4
Showing
1 changed file
with
36 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,39 @@ | ||
# CDSImport | ||
Import the schema and data from an Access Web App into a Common Data Service database. Understands specifics of the source database and supports relationships and images. | ||
# Access Web App Samples | ||
|
||
### Overview | ||
**CDSImport** contains one primary commandlet **Import-CDSAccessWebApp**. | ||
* Northwind - The result of importing the Access desktop Northwind template into an Access Web App. | ||
|
||
This module builds on top of [Microsoft.Xrm.Data.PowerShell](https://github.com/seanmcne/Microsoft.Xrm.Data.PowerShell), which in turns builds on [Microsoft.Xrm.Tooling.CrmConnector.Powershell](https://docs.microsoft.com/en-us/powershell/module/microsoft.xrm.tooling.crmconnector.powershell/?view=dynamics365ce-ps). It also uses the [SqlServer](https://docs.microsoft.com/en-us/sql/powershell/sql-server-powershell?view=sql-server-2017) module. | ||
## Using a sample | ||
|
||
2. Download the sample .dacpac that you are interested in. | ||
|
||
1. Create a new database in SQL Server or SQL Azure. The Azure portal or SQL Server Management Studio are good tools for this. Remember the database name you used. | ||
|
||
2. Install sqlpackage.exe. If you have install SQL Server Management Studio, it is already included in that distribution. Or you can install using these directions: [https://docs.microsoft.com/en-us/sql/tools/sqlpackage-download?view=sql-server-2017](https://docs.microsoft.com/en-us/sql/tools/sqlpackage-download?view=sql-server-2017) | ||
|
||
3. Full documentation on sqlpackage is available at [https://docs.microsoft.com/en-us/sql/tools/sqlpackage?view=sql-server-2017](https://docs.microsoft.com/en-us/sql/tools/sqlpackage?view=sql-server-2017) | ||
|
||
4. Run | ||
|
||
sqlpackage /a:publish /sf:sample.dacpac /tsn:servername /tdn:databasename /tu:username /tp:userpassword | ||
|
||
5. Wait. It takes a while for the tool to perform its steps. While it is operating, it will produce a list of actions it is performing and a final "success" message at the end. | ||
|
||
6. You now have the schema and data of your AWA moved to SQL. | ||
|
||
## Creating a sample | ||
|
||
To create your own sample .dacpac from an Access Web App: | ||
|
||
1. Open the AWA from Access Desktop. | ||
|
||
2. Go to the File Menu, select Save As. | ||
|
||
4. Under the default Save Database As, and Save as Snapshot. | ||
|
||
5. Name the snapshot and select a file location. | ||
|
||
6. The resulting file will have a .app extension. Using the Windows explorer, rename this file with a .zip extension. | ||
|
||
7. Open the zip file using Windows explorer or another tool. You will discover within an appdb.dacpac file. This is the file you seek that contains the AWA's schema and data. | ||
|
||
|