Install and Configure Zpl Printer on D365 F&O

 

Setup Zpl Printer On D365 F&O

Posted on

Recently, I have had an opportunity review the possibilities to print license plates within D365.  Unfortunately, there is no peripheral simulator available in Microsoft Dynamics 365 for Finance and operations. But there is an ability to do a tricky move by setting up the Zpl printer Chrome extension.

Use the link below to install Zpl printer Chrome extension:

https://chrome.google.com/webstore/detail/zpl-printer/phoidlklenidapnijkabnfdgmadlcmjo

Once you install that, keep it running.

Go to Control pane > Devices and Printers on your laptop.

Click Add a printer button.

Click The printer that is I want isn’t listed link.

Click Add a local printer or network printer with manual settings.

Click Create a new port.

Choose Type of port = Standard TCP/IP port.

Click Next button.

Set Host name or IP address = 127.0.0.1

Keep Query the printer and automatically select the driver to use as YES.

Click Next button.

Wait until Detecting TCP/IP port operation is completed.

Select Device type = Custom.

Click on Settings button.

Make sure that:

Port name = 127.0.0.1

Printer name or IP address = 127.0.0.1

Protocol = RAW

Port number = 9100

Click OK button.

Click Next button.

In the Install the printer driver, select Generic / Text only.

Click Next button.

In the Printer name, type in the Printer name like Zebra printer.

Click Next button.

Set Do not share this printer.

Click Next button.

Click Finish button.

Go to Organization administration > Setup > Network printers.

Click Download document routing agent installer.

Open document routing agent installer.

Click Next button.

Read End-user agreement and set I accept the terms in the License Agreement.

Click Next button.

Keep Destination folder as suggested by wizard.

Click Next button.

Click Install button.

Wait until completed.

Click Finish button.

Open Document routing app installed on desktop.

No need to sign in.

Click Settings button.

In the Dynamics 365 URL set URL address of the D365FO environment.

In the Azure AD Tenant set tenant of the D365FO environment.

Click OK button.

Reopen Document routing app installed on desktop.

Sign in using your credentials.

Click Printers button.

Set flag next to Zebra printer.

Click Register button.

Go to Organization administration > Setup > Network printers.

Change Active flag to YES.

If you want to print something, do not close ZPL Printer and Document routing apps. They both should be up and running.

D365 F&O Data Refresh from Tier 2 to Tier 1

Download bacpac file from LCS

select project->asset library-> database backup

1. Download the  DacFramework.msi installer for Windows. Install it 

2. download sqlpackage for Windows. "https://learn.microsoft.com/en-us/sql/tools/sqlpackage/sqlpackage-download?view=sql-server-ver15"

        extract the zip file  in below path

        extract here: C:\Program Files\Microsoft SQL Server\SQL Packages

3.      Copy your bacpac file in "J:\MSSQL_BACKUP"

4.      Open command prompt as admin and do below steps.

        cd C:\Program Files\Microsoft SQL Server\SQL Packages

SqlPackage.exe /a:import /sf:"I:\MSSQL_BACKUP\axbackup.bacpac" /tsn:localhost /tdn:AXDB_0111 /p:CommandTimeout=800 /TargetTrustServerCertificate:True

5  Execute the commands to swap the db names

a. To rename the existing db to new db 

USE [master];

GO

ALTER DATABASE [AxDB] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

GO

EXEC sp_renamedb N'AxDB', N'AxDB_Old_0111'--- if it thow error stop. Turn off the Microsoft batch services and world wide web publishing service

b.Rename the new db with the AxDB

EXEC sp_renamedb N'AXDB_0111', N'AxDB';

go

c. Set db in multiuser mode

USE [master];

GO

ALTER DATABASE [AxDB] SET multi_USER WITH ROLLBACK IMMEDIATE;

GO

6.We can do adminprovisioning from below 

>>Go to K>AOS>packagelocaldirectory>bin > AdminUserprovicsioning

7 Then do full build and synchronise the database 

8 check the below services 

  1.world wide web publishing service

  2.Microsoft Dynamics 365 Unified Operations: Batch Management Service

  3. IIS AOS services

if status is showing as stopped just start the service

9. check the client. It should be accessible.

 

D365 F&O Data refresh from Tier 1 to Tier 2 environment

RESTORE DATABASE [AxDB_Copyexport] FROM DISK = N'J:\MSSQL_BACKUP\DHG_datadrop_2_20210916.bak' WITH REPLACE, FILE = 1,

MOVE N'AXDBBuild_Data' TO N'G:\MSSQL_DATA\AxDB_Copyexport.mdf',

MOVE N'AXDBBuild_Log' TO N'H:\MSSQL_LOGS\AxDB_Copyexport_Log.ldf',

NOUNLOAD, STATS = 5

Use AxDB_Export

update sysglobalconfiguration

set value = 'SQLAZURE'

where name = 'BACKENDDB'

Use AxDB_Export

update sysglobalconfiguration

set value = 1

where name = 'TEMPTABLEINAXDB'

Use AxDB_Export

drop procedure if exists XU_DisableEnableNonClusteredIndexes

drop procedure if exists SP_ConfigureTablesForChangeTracking

drop procedure if exists SP_ConfigureTablesForChangeTracking_V2

Use AxDB_Export

drop schema [NT AUTHORITY\NETWORK SERVICE]

Use AxDB_Export

drop user [NT AUTHORITY\NETWORK SERVICE]

Use AxDB_Export

drop user axdbadmin

drop user axdeployuser

drop user axmrruntimeuser

drop user axretaildatasyncuser

drop user axretailruntimeuser

drop user axdeployextuser

update dbo.RETAILHARDWAREPROFILE set SECUREMERCHANTPROPERTIES = null where SECUREMERCHANTPROPERTIES is not null

cd C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin

SqlPackage.exe /a:export /ssn:localhost /sdn:AxDB_Export /tf:J:\MSSQL_BACKUP\DHG_cutover_rehearsal_2_20220104.bacpac /p:CommandTimeout=1200 /p:VerifyFullTextDocumentTypesSupported=false

D365 F&O delete TFS workspaces and re-assign to new developer

Easy way : 

1- Close Visual Studio

2- Open Run (Win+R) and paste one by one the following and delete anything inside:

    %localappdata%\Microsoft\Team Foundation\6.0\Cache\

    %localappdata%\Microsoft\VisualStudio

    %localappdata%\Microsoft\VSCommon

3- Restart your VM

4- Open visual studio and configure with new account

Painful way:

1- Close Visual Studio

2- Open Run (Win+R) and paste one by one the following and delete anything inside:

    %localappdata%\Microsoft\Team Foundation\6.0\Cache\

    %localappdata%\Microsoft\VisualStudio

    %localappdata%\Microsoft\VSCommon

3- Open command and run following commands:

• Goto IDE folder where the workspace program exist
  Cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
• Check all the current workspaces
  tf workspaces /server:https://dev.azure.com/{org} /computer:{ComputerName} /owner:* /format:detailed
• If you see any ghost workspace delete it
  tf workspace /delete /server:https://https://dev.azure.com/{org} '{WorkspaceName};{UserName}
  
  if above command give error run it with user id instead of username
  tf workspace /delete /server:https://https://dev.azure.com/{org} '{WorkspaceName};{UserId}

• Run this command to sure it's deleted
  tf workspaces /server:https://dev.azure.com/{org} /computer:{ComputerName} /owner:* /format:detailed

4- Restart your VM

5- Open visual studio and configure with new account

D365 Finance & Operation Change colour based on the environment

D365  Finance & Operation  Change color based on the environment


Step 1:

1. Log into a D365 F&O environment  as a systems administrator and navigate to your Settings > User options:

The system displays:

Creating a Label file in D365 Finance & Operations

Creating a Label file in D365 Finance & Operations

To create the label file, follow these steps:

1. Right-click on the project and select Add | New item... or use the keyboard

shortcut, Ctrl + Shift + A.

2. Choose Labels and Resources from the Operations Artifacts list.

3. From the list on the left, select Label File.

4. In the Name field, enter a short, but unique label name “Your Own Label Name”

5. Press Add.

6. In the Label file wizard, leave Label file ID as default.

It seems that we can specify a different name in this step, but the

previous only called this wizard with a suggested file name. The Label

file ID field contains both the ID and the file name that will be created.

7. Press Next.

8. In the language selection, move the languages from the left-hand list into the

right-hand list using the buttons. Only leave languages selected that you will

maintain. This involves creating a label in each language file.

This also applies to language with subtle differences, such as English

and Spanish. Even though the label will often be the same, we still

need to manually maintain each language file. Currently this also

means we have to be careful to ensure we give them the correct ID.

9. Press Next.

10. Check that the Summary page is correct, and press Finish.

Creating a new Model and Packages in D365 Finance & Operations

Creating a new Model and Packages in D365 Finance & Operations

1. Under the Dynamics 365 menu, choose Model Management | Create model....

2. The Model name is named as we would in AX 2012, and should be named like a

new type, such as <prefix><area/module><ShortName>.

3. Complete the first steps as follows:

Field Value

Model name  : In our case, our company is called Contoso, so our prefix will be Con,

the area of change is an existing module (WHS) and it is for general

extensions (extending standard objects without the customization).

It is therefore named ConWHSGeneralExtensions. You should use

your own prefix and prefixes, and the name for explained further in

the There's more... section.

Model publisher : Your organization's name.

Layer As follows:

ISV / vertical solution / add-on: ISV

VAR / Partner solution / add-on: VAR

Customer solution / add-on: CUS or USR

Version Leave as 1.0.0.0

You can update this to maintain a version of the model. This does not

auto-increment and is usually left as default.

Model description

A full description of the model for other developers to read.

Starting a New Project

Model display name :

Leave as default, which should be the Model name.

4. Press Next.

5. In the Select package page, choose Create new package.

If you choose Select existing package, it will mean that your model

will be placed under the package and is intended to over-layer the

elements in in that package. You cannot over-layer elements in

extension projects, but unless we absolutely must over-layer, always

choose Create new package.

6. Press Next.

7. We are now offered a list of packages that we can reference, these are listed as

package's name and the models that the package contains, check

ApplicationSuite and press Next.

Most of the elements in Operations are in ApplicationSuite; so,

unless our package doesn't need any standard, type this will always be

selected. The others we would select based on the elements we know

we will use. We can add more package references later, but if we know

which elements we will use, it saves some time..

8. The two check boxes, Create new project and Make this my default model for

new projects, should both be checked.

9. Press Finish.

10. This opens the New Project dialog. The project name is usually the same as the

package and Model name; then, enter the package name in the Name field.

11. The Location field must be changed; it will create the project in the default project

folder, but we linked C:Projects<initials/username> to source control. The

project must be created under this folder. So, in my case, Location must be

C:ProjectsSB.

12. The Solution name field should be left as the project name.

13. Ensure that both Create directory for solution and Add to source control are

checked.

14. Press OK.