Page History
...
There can be issues with data types when loading data through Fabric Data Factory.In such cases, the Fabric pipeline will display an error, suggesting using varchar(8000) for the affected column (e.g., “”). The user should update the column’s data type to match the recommendation from Data Factory.After making the changes, the table should be recreated, the script regenerated,and the pipeline executed again with the extended property “Recreate Pipeline on run” set to “True” or left blank.
Post Install Steps – Optional
If you used the script Setup Wizard for installation then the following optional post-install steps are available.
Configure Connections
These connections added that will optionally require your attention:
- Connection: Data Warehouse ('Fabrics') - This connection was setup as per parameters provided in Setup Wizard
- open Properties and click derive button for Database Host/Server and Database ID.
- open it's properties and check extended properties tab, set it up for Blob Storage Account , Blob Storage Container and Blob Storage SAS Key
- Connection: 'Database Source System' - this connection was setup as an example source connection,
- open its properties and set it up for a source DB in your environment
- or you can remove it if not required
Enable Script Launcher Toolbar
There are a number of stand-alone scripts which provide some features such as "Ranged Loading", these scripts have been added to the Script Launcher menu but you will need to enable the menu toolbar item to see them.
To enable the Script Launcher menu in RED: Select menu item Home > Script Launcher
Source Enablement Pack Support
| Source Pack Name | Supported By Microsoft Fabric | Supported Features | Prerequisites/Permissions Required for Microsoft Fabric |
|---|---|---|---|
| Google Cloud Storage | Yes | Download to local and load | None |
| Yes | Download to local and load | None | |
| Amazon S3 | Yes | Download to local and load | None |
| Windows Parser | Yes | Load Template, Source Properties will have option to select parser type to load the files. | Refer to Windows Parser Guide |
| Azure One Lake | Yes | Download to local and load | Refer to Windows Parser Guide |
Troubleshooting and Tips
Run As Administrator
Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select "Run As Administrator"
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack to using the 'cd' command:
| No Format |
|---|
C:\Windows\system32> cd <full path to the unpacked folder> |
Run batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and hit enter, for example:
| No Format |
|---|
C:\temp\EnablementPack>install_WslPowershell_Modules.bat |
Run Powershell (.ps1) scripts from the administrator prompt by typing the Powershell run script command, for example:
| No Format |
|---|
C:\temp\EnablementPack>Powershell -ExecutionPolicy Bypass -File .\Setup_Enablement_Pack.ps1 |
| Note | ||
|---|---|---|
| ||
| In the event you can not bypass the Powershell execution policy due to group policies you can instead try "-ExecutionPolicy RemoteSigned" which should allow unsigned local scripts. |
Windows Powershell Script Execution
On some systems Windows Powershell script execution is disabled by default. There are a number of workarounds for this which can be found by searching the term "Powershell Execution Policy".
Here is the most common workaround which WhereScape suggests, which does not permanently change the execution rights:
Start a Windows CMD prompt as Administrator, change directory to your script directory and run the WhereScape Powershell scripts with this command:
| No Format |
|---|
cmd:>Powershell -ExecutionPolicy Bypass -File .\<script_file_name.ps1> |
Re-install Python Libraries
Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select "Run As Administrator"
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack to using the 'cd' command:
| No Format |
|---|
C:\Windows\system32> cd <full path to the unpacked folder> |
Run batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and hit enter, for example:
| No Format |
|---|
C:\temp\EnablementPack>uninstall_WslPython_Modules.bat |
For installation of Python libraries there are two methods
- Method 1
Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select "Run As Administrator"
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack to using the 'cd' command:
| No Format |
|---|
C:\Windows\system32> cd <full path to the unpacked folder> |
Run batch (.bat) scripts from the administrator prompt by simply typing the name at the prompt and hit enter, for example:
| No Format |
|---|
C:\temp\EnablementPack>install_WslPython_Modules.bat |
- Method 2
Press the Windows Key on your keyboard and start typing cmd.exe, when the cmd.exe icon shows up in the search list right click it to bring up the context menu, select "Run As Administrator"
Now you have an admin prompt navigate to to the folder where you have unpacked your WhereScape Red Enablement Pack to using the 'cd' command:
| No Format |
|---|
C:\Windows\system32> cd <full path to the unpacked folder> |
Run the below command
| No Format |
|---|
python -m pip install -r requirements.txt |
