Tag: Subscription

AL, Business Central, Codeunit, Dataverse, Events, Extension, Integration, Procedures, Subscription, VS Code

Create Integration Codeunit for Business Central & Dataverse Integration

Ashwini Tripathi
Overview
Step-1
Step-2
Step-3
Step-4
Step-5
step-6
step-7
step-8
step-9
step-10
Testing

This is the Seventh post in the series. If you want to go to previous post click here.

From the series of steps this post is dedicated to Step-6:

As a Sixth Step we will Create Integration Codeunit in Business Central

codeunit 50120 CDSDataverseEvent
{
}

Add these Procedures

local procedure LookupCDSProspect(SavedCRMId: Guid; var CRMId: Guid; IntTableFilter: Text): Boolean
    var
        CDSProspect: Record "CDS cr95d_Prospects";
        OriginalCDSProspect: Record "CDS cr95d_Prospects";
        OriginalCDSProspectList: Page "CDS Prospect List";
    begin
        if not IsNullGuid(CRMId) then begin
            if CDSProspect.Get(CRMId) then
                OriginalCDSProspectList.SetRecord(CDSProspect);
            if not IsNullGuid(SavedCRMId) then
                if OriginalCDSProspect.Get(SavedCRMId) then
                    OriginalCDSProspectList.SetCurrentlyCoupledCDSProspect(OriginalCDSProspect);
        end;

        CDSProspect.SetView(IntTableFilter);
        OriginalCDSProspectList.SetTableView(CDSProspect);
        OriginalCDSProspectList.LookupMode(true);
        if OriginalCDSProspectList.RunModal = ACTION::LookupOK then begin
            OriginalCDSProspectList.GetRecord(CDSProspect);
            CRMId := CDSProspect.cr95d_ProspectsId;
            exit(true);
        end;
        exit(false);
    end;

local procedure AddEntityTableMapping(CRMEntityTypeName: Text; TableID: Integer; var TempNameValueBuffer: Record "Name/Value Buffer" temporary)
    begin
        TempNameValueBuffer.Init();
        TempNameValueBuffer.ID := TempNameValueBuffer.Count + 1;
        TempNameValueBuffer.Name := CopyStr(CRMEntityTypeName, 1, MaxStrLen(TempNameValueBuffer.Name));
        TempNameValueBuffer.Value := Format(TableID);
        TempNameValueBuffer.Insert();
    end;

local procedure InsertIntegrationTableMapping(var IntegrationTableMapping: Record "Integration Table Mapping"; MappingName: Code[20]; TableNo: Integer; IntegrationTableNo: Integer; IntegrationTableUIDFieldNo: Integer; IntegrationTableModifiedFieldNo: Integer; TableConfigTemplateCode: Code[10]; IntegrationTableConfigTemplateCode: Code[10]; SynchOnlyCoupledRecords: Boolean)
    begin
        IntegrationTableMapping.CreateRecord(MappingName, TableNo, IntegrationTableNo, IntegrationTableUIDFieldNo, IntegrationTableModifiedFieldNo, TableConfigTemplateCode, IntegrationTableConfigTemplateCode, SynchOnlyCoupledRecords, IntegrationTableMapping.Direction::Bidirectional, 'CDS');
    end;

procedure InsertIntegrationFieldMapping(IntegrationTableMappingName: Code[20]; TableFieldNo: Integer; IntegrationTableFieldNo: Integer; SynchDirection: Option; ConstValue: Text; ValidateField: Boolean; ValidateIntegrationTableField: Boolean)
    var
        IntegrationFieldMapping: Record "Integration Field Mapping";
    begin
        IntegrationFieldMapping.CreateRecord(IntegrationTableMappingName, TableFieldNo, IntegrationTableFieldNo, SynchDirection,
            ConstValue, ValidateField, ValidateIntegrationTableField);
    end;

To Add Event Subscriptions, Use the new Shift+Alt+E shortcut in the AL code editor to invoke a list of all events.

Search for Event OnGetCDSTableNo – “CRM Setup Defaults”

[EventSubscriber(ObjectType::Codeunit, Codeunit::"CRM Setup Defaults", 'OnGetCDSTableNo', '', false, false)]

local procedure OnGetCDSTableNo(BCTableNo: Integer; var CDSTableNo: Integer; var handled: Boolean);
    begin
        if BCTableNo = DATABASE::"Prospect" then begin
            CDSTableNo := DATABASE::"CDS cr95d_Prospects";
            handled := true;
        end;
    end;

Search for Event OnLookupCRMTables – “Lookup CRM Tables”

[EventSubscriber(ObjectType::Codeunit, Codeunit::"Lookup CRM Tables", 'OnLookupCRMTables', '', false, false)]

local procedure OnLookupCRMTables(CRMTableID: Integer; NAVTableId: Integer; SavedCRMId: Guid; var CRMId: Guid; IntTableFilter: Text; var Handled: Boolean);
    begin
        if CRMTableID = Database::"CDS cr95d_Prospects" then
            Handled := LookupCDSProspect(SavedCRMId, CRMId, IntTableFilter);
    end;

Search for Event OnAddEntityTableMapping – “CRM Setup Defaults”

[EventSubscriber(ObjectType::Codeunit, Codeunit::"CRM Setup Defaults", 'OnAddEntityTableMapping', '', false, false)]

local procedure OnAddEntityTableMapping(var TempNameValueBuffer: Record "Name/Value Buffer");
    begin
        AddEntityTableMapping('Prospect', DATABASE::"CDS cr95d_Prospects", TempNameValueBuffer);
    end;

Search for Event OnAfterResetConfiguration – “CDS Setup Defaults”

[EventSubscriber(ObjectType::Codeunit, Codeunit::"CDS Setup Defaults", 'OnAfterResetConfiguration', '', false, false)]

local procedure OnAfterResetConfiguration(CDSConnectionSetup: Record "CDS Connection Setup");
    var
        IntegrationTableMapping: Record "Integration Table Mapping";
        IntegrationFieldMapping: Record "Integration Field Mapping";
        CDSProspect: Record "CDS cr95d_Prospects";
        Prospect: Record "Prospect";
    begin
        InsertIntegrationTableMapping(
            IntegrationTableMapping, 'Prospect',
            DATABASE::"Prospect", DATABASE::"CDS cr95d_Prospects", CDSProspect.FieldNo(cr95d_ProspectsId), CDSProspect.FieldNo(ModifiedOn), '', '', true);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo("No."), CDSProspect.FieldNo(cr95d_ProspectsId), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo(Name), CDSProspect.FieldNo(cr95d_ProspectName), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo(Probability), CDSProspect.FieldNo(cr95d_Probability), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo("Contract Amount"), CDSProspect.FieldNo(cr95d_ContractAmount), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo("Contract Amount (Base)"), CDSProspect.FieldNo(cr95d_contractamount_Base), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo(Stage), CDSProspect.FieldNo(cr95d_Stage), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo("Forecast Revenue"), CDSProspect.FieldNo(cr95d_ForcastedRevenue), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);

        InsertIntegrationFieldMapping('Prospect', Prospect.FieldNo("Forecast Revenue (Base)"), CDSProspect.FieldNo(cr95d_forcastedrevenue_Base), IntegrationFieldMapping.Direction::Bidirectional, '', true, false);
    end;

Now you are good to proceed with Next Step.

You can jump to Next Step from here.

Overview
Step-1
Step-2
Step-3
Step-4
Step-5
step-6
step-7
step-8
step-9
step-10
Testing
Advertisement
AL, BC18, Business Central, Code, Codeunit, Combinations, Development Tips, Dimension, Dynamics 365, Environment, Events, Extension, Extension Package, How To, Online, Page, Sandbox, Subscription, Table, Tip & Tricks, VS Code

Walkthrough Extension Development in Online Sandbox – Business Central

Ashwini Tripathi

I have my Sandbox environment as below:

Details of the Sandbox as below:

Connecting VS code to above environment.

When you try to Publish the extension, it will ask you to authenticate.

Copy the Link and open in the browser and paste the code in the box as shown below.

Next it will ask for your Online Instance User Id & Password provide it and on confirmation close the page. It will start deploying the extension.

In this walkthrough I am using below scenario:

Requirement is we need to be able to define some code for dimension combinations. Let me say it will be Sales Code, you can choose name of your choice, this is not Salesperson code.

I am assuming these dimensions will follow the sequence as defined on my General Ledger Setup as below:

On Sales Order & Invoice user should be able to select this Sales Code and dimensions should be populated on order accordingly.

For tracking purpose this Sales Code should flow to Posted Sales Invoice and Customer Ledger.

So, Let’s Start with the development process:

Step-1 We will Create the Table

Here is the code for LookupDimValue Function, it will set filter for Dimension Code on Dimension Value table, as per the Dimension No passed. (1 is for Shortcut Dimension defined on General Ledger Setup, similarly for other 8 dimensions)

Step-2 Next, we will create the Page for this Setup

Step-3 Next, we will add the Sales Code field to all required Tables & Pages

Here is the code for AddDim Function. It is assumed that only combination provided in Sales Code Setup will be used. If you have defined Default dimensions or Combinations, those need to be preserved else this code will overwrite them. You will have to find the Data Set Entry, store them in temporary table used in below code and then add all the dimensions from the setup.

When you Select Sales Code on the Order or Invoice it will populate all the dimensions defined in the Setup.

Code for other Tables & Pages

Step-4 Next, we need to take care to flow the Sales Code to the Ledger and Posted documents.

For posted documents we need not to worry it will flow automatically provided we have defined the fields on same Id.

However, for ledger we will require to use Events to pass the data to their destinations. In this case we are only passing to Customer Ledger Entry. For this we will create a Codeunit.

To Add Event Subscriptions, Use the new Shift+Alt+E shortcut in the AL code editor to invoke a list of all events.

Search for the even you are looking for.

When pressing Enter to select an event entry, an event subscriber for the event will be inserted at the cursor position in the active AL code editor window.

Here is the Codeunit Code:

This is not the final code; much more can be done or need to be done before it can be delivered to customer for their use. Purpose of this walkthrough was to demo the way we can customize the solution using extensions and publishing to Online tenant in Sandbox.

Hope you enjoyed the information. Will come with more similar information in my next posts. Till then keep exploring, learning and sharing your knowledge with others.

Remain safe, take care of your loved ones, put your mask, maintain safe distance and don’t forget to get vaccinated.

Business Central, Information, License, upgrade

Those planning for Upgrade – Some Important Information

Ashwini Tripathi

As per the roadmap which Microsoft has published for Business Central, it shows that the Business Central product name will be continued for future. It means there will not be a Dynamics NAV 2019.

BC Road-map

Looking at your investment in terms of license and annual BREP, it is sense able to upgrade to Microsoft Dynamics 365 Business Central, whether your solution is deployed in Cloud or on-premises.

Don’t take me wrong I don’t mean to say that Microsoft Dynamics NAV and Dynamics 365 for finance and operations, Business edition are now obsolete.

Microsoft is not closing support to these products, it is still available to them. Only any new updates to these solutions we cannot expect any more.

One important note: New customers will still be able to purchase Microsoft Dynamics NAV 2018 till 31st March 2019. Same concept of concurrent user license with starter/extended pack.

From 1st April new customers will not be able to license NAV 2018, but existing NAV customers using the solution can still be able to purchase additional licenses as per their requirements if any.

If you missed earlier post do check this Link also.

 

What had changed in license model for Dynamics 365 Business Central

 

One change that a major one is now no more Concurrent licenses, new license purchased will be for named user.

One user one license, however named user will be able to access the application from multiple devices.

As earlier starter & extended pack was available now it will be Essentials and Premium.

Stander version of Business Central is termed as Essentials while with additional modules Service and Manufacturing is termed as Premium.

When comes to licensing you are not allowed to mix and match essentials & premium licenses, it should be from either of them.

Where is Limited user? Don’t worry it have been taken care as Team Member License. Read access throughout the application and write access to maximum of three tables excluding General Ledger entries.

License can be purchased as Perpetual or Subscription basis.

Licenses for Business Central differ from Dynamics NAV licenses in several ways:

  • Dynamics NAV licenses are calculated from concurrent users, where multiple users can share a license. Business Central licenses, on the other hand, are calculated from named users
  • With Business Central it is no longer necessary to have a Starter Pack. As a minimum, you need a Premium or Essentials user
  • It is only possible to have either Premium or Essentials users in your license. You can purchase Teams Members for both Premium and Essentials licenses.

 

What deployment options are available?

  1. Perpetual License – On premises
  2. Perpetual License – Cloud
  3. Subscription License – On premises
  4. Subscription License – Cloud
  5. Software As A Service (SaaS)

 

When you can upgrade to Microsoft Dynamics Business Central?

 

Microsoft Dynamics 365 Business Central is now generally available worldwide for cloud, and on-premises deployments. However you can check if it is available for your country from your local partners.

Local Functionality in Dynamics 365 Business Central

You can go-ahead with upgrade planning whenever you want too. Just get in touch with your current ERP provider.

For free lancing upgrade/development tasks you can contact us too at KSD Consultancy Private Limited. We are taking new project booking till 31st March on our old price, could be fixed or hour basis, which ever suitable to you. You can save lot from your local partners cost.

 

What’s on offer for existing customers?

 

Customers up-to-date with their BREP can upgrade to Dynamics 365 Business Central on-premises using LMT Upgrade.

Due to change in licensing model in Business Central. Below you can see exchange rate from perpetual NAV concurrent license to Business Central named user licenses.

If you have purchased your Dynamics NAV with Perpetual Licencing before October 1, 2018, your current NAV licenses will be converted from:

  • One Full User in Extended Pack to two Premium users
  • One Full user to two Essentials users
  • One Limited user to one Team Member

In addition to the converting of licenses, the licensing setup is different. As mentioned, Dynamics NAV licenses are calculated from concurrent users, where multiple users can share a number of licenses. Business Central licenses, on the other hand, are calculated from named users. The total value of your current licenses will remain the same – even after the conversion.

For more details on Licensing please refer here, make sure you always check with latest version of documents or discuss with your partner for current effective offers.

Dynamics 365 Business Central on-premises Upgrade Policy​

Dynamics 365 Business Central on-premises Licensing Guide

Similar to Dynamics NAV, the functionality of the D365 Business Central is divided into two ‘packages’, Essentials and Premium. The functionality of ‘Essentials’ corresponds to NAV’s ‘Starter Pack’ and the functionality of ‘Premium’ corresponds to NAV’s ‘Extended Pack’

Brief idea as below:

D365 Business Central Essentials /
Dynamics NAV Starter Pack
D365 Business Central Premium /
Dynamics NAV Extended

Financial Management

General Ledger
Cash Management
Fixed Assets
Currencies
Consolidation

Financial Management Extended

Inter-Company (Essentials)
Cost Accounting (Essentials)

Supply Chain Management

Sales Order processing
Purchase and procurement
Item management
Locations
Basic Warehousing

Supply Chain Management
Extended

Advanced Warehousing (Essentials)

Jobs and Resources

Job Planning, Budgets and Invoicing
Resource allocations
Timesheets

 

Contact

Management Contacts
Campaigns
Opportunity Management
D365 Sales Integration

Service Management

Service Contracts
Service Items
Service Order Management

Assembly

Assembly Bill of Materials

Manufacturing

Production BOMs
Works order management
Capacity and Demand planning

It will be always advised to verify before you make up your mind. However you can trust to Microsoft links provided in above post.

 

Data, Development Tips, How To, Information, Instalation & Configuration, Replication, SQL, Tip & Tricks

Database Replication – Part V

Ashwini Tripathi

This post is in continuation to my earlier post. Please check if you missed.

Database Replication – Part I

Database Replication – Part II

Database Replication – Part III

Database Replication – Part IV

As committed in this post we will continue to cover practical approach, Next step from last post.

We will create a subscription using SQL Server Management Studio

To create the subscription

  • Connect to the Publisher in SQL Server Management Studio, expand the server node, and then expand the Replication folder.
  • In the Local Publications folder, right-click the Nav2018ItemTrans publication, and then click New Subscriptions.

DR-39

The New Subscription Wizard launches.

DR-40

  • On the Publication page, select Nav2018ItemTrans, and then click Next.

DR-41

  • On the Distribution Agent Location page, select Run all agents at the Distributor, and then click Next.

DR-42

  • On the Subscribers page, if the name of the Subscriber instance is not displayed, click Add Subscriber, click Add SQL Server Subscriber, enter the Subscriber instance name in the Connect to Server dialog box, and then click Connect.
  • On the Subscribers page, select the instance name of the Subscriber server, and select under Subscription Database.
  • On the New Database dialog box/Select from Drop Down List, enter Nav2018ReplDatabase in the Database name box, click OK, and then click Next.

DR-43

  • In the Distribution Agent Security dialog box, click the ellipsis (…) button, enter <Machine_Name>\repl_distribution in the Process account box, enter the password for this account, click OK.

DR-44

  • Click Next.

 

DR-45DR-46DR-47DR-48DR-49

  • Click Finish to accept the default values on the remaining pages and complete the wizard.

Setting database permissions at the Subscriber

  • Connect to the Subscriber in SQL Server Management Studio, expand Databases, Nav2018ReplDatabase, and Security, right-click Users, and then select New User.
  • On the General page, in the User type list, select Windows user.
  • Select the User name box and click the ellipsis (…) button, in the Enter the object name to select box type <Machine_Name>\repl_distribution, click Check Names, and then click OK.

DR-50

  • On the Membership page, in Database role membership area, select db_owner, and then click OK to create the user.

DR-51

When setting up SQL Server replication you might see an error message from the Transactional Replication Log Reader Agent which reads like the following.

Error messages:

  • The process could not execute ‘sp_replcmds’ on ”. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011
  • Cannot execute as the database principal because the principal “dbo” does not exist, this type of principal cannot be impersonated, or you do not have permission. (Source: MSSQLServer, Error number: 15517) Get help: http://help/15517
  • The process could not execute ‘sp_replcmds’ on ”. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037) Get help: http://help/MSSQL_REPL22037

Often this error message can come from the database not having a valid owner, or the SQL Server is not being able to correctly identify the owner of the database.

Often this is easiest to fix by changing the database owner by using the sp_changedbowner system stored procedure as shown below. The sa account is a reliable account to use to change the ownership of the database to.

USE PublishedDatabase

GO

EXEC sp_changedbowner ‘sa’

GO

Once the database ownership has been changed the log reader will probably start working right away. If it doesn’t quickly restarting the log reader should resolve the problem.

While this does require changes to the production database, there is no outage required to make these changes.

To view the synchronization status of the subscription

  • Connect to the Publisher in SQL Server Management Studio, expand the server node, and then expand the Replication folder.
  • In the Local Publications folder, expand the Nav2018ItemTrans publication, right-click the subscription in the Nav2018ReplDatabase database, and then click View Synchronization Status.

DR-52

The current synchronization status of the subscription is displayed.

DR-53

  • If the subscription is not visible under Nav2018ItemTrans, press F5 to refresh the list.

Validating the Subscription and Measuring Latency

We will use tracer tokens to verify that changes are being replicated to the Subscriber and to determine latency, the time it takes for a change made at the Publisher to appear to the Subscriber.

To insert a tracer token and view information on the token

  • Connect to the Publisher in SQL Server Management Studio, expand the server node, right-click the Replication folder, and then click Launch Replication Monitor.
  • Replication Monitor launches.
  • Expand a Publisher group in the left pane, expand the Publisher instance, and then click the Nav2018ItemTrans publication.
  • Click the Tracer Tokens tab.
  • Click Insert Tracer.
  • View elapsed time for the tracer token in the following columns: Publisher to Distributor, Distributor to Subscriber, Total Latency. A value of Pending indicates that the token has not reached a given point.

DR-54

This way we are done with Database Replication Setup.

Will come up with more topic soon.

 

Data, Development Tips, How To, Information, Replication, SQL, Tip & Tricks

Database Replication – Part IV

Ashwini Tripathi

This post is in continuation to my earlier post. Please check if you missed.

Database Replication – Part I

Database Replication – Part II

Database Replication – Part III

As committed in this post we will continue to cover practical approach, Next step from last post.

Publishing Data Using Transactional Replication

We will create a transactional publication using SQL Server Management Studio to publish a filtered subset of the Item table in the Nav 2018 sample database. We will also add the SQL Server login used by the Distribution Agent to the publication access list (PAL).

To create a publication and define articles

Connect to the Publisher in SQL Server Management Studio, and then expand the server node.

Expand the Replication folder, right-click the Local Publications folder, and click New Publication.

DR-24

The Publication Configuration Wizard launches.

DR-25

On the Publication Database page, select Nav 2018 database, and then click Next.

DR-26

On the Publication Type page, select Transactional publication, and then click Next.

DR-27

On the Articles page, expand the Tables node, select the check box for table CRONOUS International Ltd_$Item (dbo). Click Next.

DR-28

On the Filter Table Rows page, click Add.

In the Add Filter dialog box, click the Replenishment System column, click the right arrow to add the column to the Filter statement WHERE clause of the filter query, and modify the WHERE clause as follows:

WHERE [Replenishment System] = 1

Click OK,

DR-29

Click Next.

DR-30

Select the Create a snapshot immediately and keep the snapshot available to initialize subscriptions check box, and click Next.

DR-31

On the Agent Security page, clear Use the security settings from the Snapshot Agent check box.

Click Security Settings for the Snapshot Agent, enter <Machine_Name>\repl_snapshot in the Process account box, supply the password for this account, and then click OK.

DR-32

Repeat the previous step to set repl_logreader as the process account for the Log Reader Agent

DR-33

Click Finish.

On the Complete the Wizard page, type Nav2018ItemTrans in the Publication name box, and click Finish.

DR-34

After the publication is created, click Close to complete the wizard.

DR-35

To view the status of snapshot generation

  • Connect to the Publisher in SQL Server Management Studio, expand the server node, and then expand the Replication folder.

In the Local Publications folder, right-click Nav2018ItemTrans, and then click View Snapshot Agent Status.

DR-36

The current status of the Snapshot Agent job for the publication is displayed. Verify that the snapshot job has succeeded.

DR-37

To add the Distribution Agent login to the PAL

  • Connect to the Publisher in SQL Server Management Studio, expand the server node, and then expand the Replication folder.
  • In the Local Publications folder, right-click Nav2018ItemTrans, and then click Properties.
  • The Publication Properties dialog box is displayed.
  • Select the Publication Access List page, and click Add.

In the Add Publication Access dialog box, select <Machine_Name>\repl_distribution and click OK. Click OK.

DR-38

 

We will discuss Next step in our upcoming post.

 

License, NAV 2018, Tip & Tricks

Microsoft Dynamics NAV 2018 Licenses

Ashwini Tripathi

You have the choice of purchasing Microsoft Dynamics NAV licenses up front, or paying a monthly fee to a service provider.

Perpetual Licensing:

  • You pay affordable upfront starting price, rapid start tools and built in functionality.
  • You license the ERP Solution functionality, and access to that functionality is secured by licensing users.

 

Perpetual License Overview

Service Provider’s Subscription Licensing:

  • You have choice to keep the upfront cost to a minimum through a “per user per month” licensing fee.
  • This helps get started with a low initial cost while leveraging the built-in functionality and rapid start tools.

 

In both licensing models

You have the choice of two Concurrent-user types –

  1. Limited User (Full Read & Limited Write)
  2. Full User (Full Read & Full Write)

Option to give those users access to advanced functionality through the “Extended Pack.”

Starter and Extended Pack License Overview

Starter Pack (Base Pack – Required)

The Starter Pack offers for one price.

  • Core Financials
  • Distributions
  • Professional Services functionality
  • 3 Full User licenses/ Concurrent CALs included
  • Additional Software licenses may be required, like Server, SQL, Office 365, SharePoint. Additional Software must be licensed according to the applicable license terms.

For many businesses, this is the only license component required.

 

Extended Pack (Optional)

The Extended Pack enables customers to integrate core financials and distribution management with broader functionality extensions such as:

  • Manufacturing to support and control the manufacturing environment
  • Warehousing to manage the warehouse to support operations
  • The first three Full Users included in the Start Pack and coming users get to access to all of the incremental functionality.
  • Starter Pack is the prerequisite to the Extended Pack

 

Packaging of Functionality

A Microsoft Dynamics NAV customer can choose whether to deploy the Starter and Extended Pack through the

  • Microsoft Windows client for Microsoft Dynamics NAV
  • Web client for Microsoft Dynamics NAV
  • Microsoft Dynamics NAV Portal framework for Microsoft SharePoint (also known as the Microsoft Dynamics NAV SharePoint client)

All through the same User types.

2018 Functionality -1

 

2018 Functionality -2

Starter Pack is for companies who need

  • Core Financials
  • Trade functionality
  • Basic Financials Management (General Ledger and Fixed Assets)
  • Basic Supply Chain Management
  • Basic Sales Management (Sales, Purchasing and Inventory)
  • Professional Services (Project management)
  • A broad set of Business Insight and reporting functionality as an integral part of the product.
  • A wide range of tools to customize the solution, to meet the needs of every customer together with deep integration opportunities to be made through web services.

 

Extended Pack is for growing, midmarket, or high-functional-needs companies who are looking for an adaptive solution with a broad set of functionality:

  • Warehousing
  • Manufacturing
  • It comes with additional customization objects for doing more extensive customizations.

 

CONFIGURATION AND DEVELOPMENT

Page Designer

  • Change existing pages and enables you to create 100 page objects (included and numbered from 50,000 to 50,099).
  • The Page Designer also enables you to use the Navigation Pane Designer. This means, for example, that you can create new menu items.
  • This module does not include access to C/AL from pages.

Report Designer

  • Change existing reports and create 100 new report objects (numbered from 50,000 to 50,099).
  • This module provides access to C/AL (the C/SIDE application language) from reports used for defining special calculations and business rules.
  • Create new reports from scratch or copy an existing report to use as a starting point.
  • This module enables you to take advantage of the functionality included for developers in the Navigation Pane Designer (for example, creating new menu items).

Table Designer

  • Change existing table definitions and create ten new tables (numbered from 50,000 to 50,009).
  • You can change properties on fields, such as the field name, decimal places, and maximum value, add new fields to existing tables, and create new tables to store data specific to your business.
  • Create keys for sorting information and change or create new FlowFields and FlowFilters for “slicing and dicing” information in new ways.
  • This module does not include access to C/AL from tables.

XMLports (100)

  • Create new or change existing XMLport objects.
  • XMLport Designer provides access to C/AL (the C/SIDE application language) from XMLports used for defining special calculations and business rules.
  • Every XMLport object in Microsoft Dynamics NAV is created using this tool and can therefore be customized easily.
  • This module enables you to create 100 new XMLport objects (numbered from 50,000 to 50,099) and to take advantage of the functionality included for developers in the
  • Navigation Pane Designer (for example, creating new menu items).

Query Designer

  • The Query Designer provides the ability to modify existing queries in the application, as well as create up to 100 new queries.
  • The Query Designer is the main tool for creating objects of the type Query.
  • Query objects retrieve subsets of data spread across the database and are data pumps for various places within the application such as charts and business logic.

 

Application Builder (A la carte)

  • Change the business rules and special calculations that work behind the scenes. Business rules and special calculations are defined in C/AL (the C/SIDE application language).
  • Although this granule includes access to C/AL, it does not permit access to existing C/AL code that updates write-protected tables (for example, postings).
  • With Application Builder, you can create entirely new areas of functionality for your application, enabling you to tailor Microsoft Dynamics NAV to fit your entire organization.
  • It also enables you to create 100 codeunit objects (numbered from 50,000 to 50,099).
  • You can also take advantage of the functionality included for developers in the Navigation Pane Designer (for example, creating new menu items).

 

Solution Developer (A la carte)

  • Change the business rules and special calculations that work behind the scenes. Business rules and special calculations are defined in C/AL (the C/SIDE application language).
  • This module provides access to code that updates write-protected tables to the Merge and Upgrade Tools.
  • You can also Change or create any object type, Use the menu options Translate/Export and Translate/ Import in the Object Designer.

(These options are not available with the Application Builder module).

 

Application Objects

Codeunits (100)

  • 10 Codeunits are included in the Starter Pack
  • 10 Codeunits are included in the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

Reports (100)

  • Additional groups of 100 are available in the Customization suite.

Tables (10)

  • 10 tables are included with the Extended Pack.
  • Additional groups of 10 are available in the Customization suite.

XMLports (100)

  • 100 XMLports are included with the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

Queries (100)

  • Additional groups of 100 are available in the Customization suite.

Pages (100)

  • 100 Pages are included with the Extended Pack.
  • Additional groups of 100 are available in the Customization suite.

 

For more details you can check here.

 

 

 

 

Azure, How To, Information, Instalation & Configuration, Tip & Tricks

AZURE free Subscription

Ashwini Tripathi

Azure-0

I will be going with few posts demonstrating the Navision in Azure environment.

To start with we will be required to subscribe to Azure first.

Open page:

https://azure.microsoft.com/en-us/free/

Click on Start now.

Azure-1

Enter your Mobile No to verify you phone no.

Azure-2

Next you will be required to verify your credit card.

Once both things are verified you can start with Sign up with the Azure Subscription.

Azure-3

Before you start with managing your services on Azure here presented few FAQ.

 

Few FAQ on Azure Subscription.

 

Why is my credit card being charged $1 for signing up for the Free Trial offer?

To ensure a valid credit card, Microsoft will charge your credit card $1 when signing up for the Free Trial Offer. This is only an authorization hold, the charge will be reversed within 3-5 business days.

What happens with the services I created after the 30-day trial period ends?

Once the trial period is over, if you have not upgraded to a Pay-As-You-Go Azure subscription, we will decommission your services, and you will not be able to use them anymore.

What do I get when I sign up for a Free Trial?

You receive a $200 credit to spend on Azure services during the trial. You can use this $200 however you want to create and try out any combination of Azure resources. It enables you to explore our cloud entirely for free.

Do I pay anything during the trial?

No – the trial is absolutely free.

Do I have to pay something at the end of the trial?

No – there is absolutely no obligation to buy anything at the end of the trial.

How do I know how much of the $200 I’ve used and how much I have left?

During the trial we display your remaining trial credits at the top of the management portal. You cannot miss it.

What happens if I exceed the $200 free trial credit?

If you exceed your $200 free credit, we will suspend your free trial account. You can optionally upgrade your trial to be a Pay-As-You-Go Azure subscription at this point if you want to continue using and paying for services. If not, don’t worry – you won’t be billed anything.

Please refer to updated FAQ on site at time of using, all information is true as on date of this post, anything can change. https://azure.microsoft.com/en-us/pricing/free-trial-faq/

Azure-4

Click Start managing my subscription, you will land to your Dashboard.

Will come with next step in my upcoming post.