Quantcast
Channel: Microsoft Dynamics 365 Community
Viewing all 7890 articles
Browse latest View live

Top Problems for Dynamics NAV Classic Client

$
0
0

Top Two Problems for Dynamics NAV Classic Client: Table Locks and Time

Microsoft Dynamics NAV Classic Client Problems - Table Locks

Two of the biggest complaints I hear from clients who are still on NAV versions prior to NAV 2013 are the headaches caused by table locks, and the time required to post sales orders. If you are one of those people suffering from either (or both) of these issues, keep reading, there is hope. With NAV 2017 – provided your custom code is written properly – the chances of either of these being a problem are pretty close to zero.

Dimensions

Prior to NAV 2013, each dimension to be recorded for a document had to be written to a table as a single record. Therefore, if you have two header dimensions and three line dimensions, a sales order that had 10 lines would create 32 records. When the sales order was posted, it would create another 32 records for the sales shipment, and another 32 records for the sales invoice.  Moreover, to add to the processing, the original records with the sales order have to be deleted when it is deleted during the posting. Therefore, for that one document, you end up with 128 records processed.

From NAV 2013 and forward, only one number, called a Dimension Set ID, is written, and it is written only once to the header. Each line can have a different dimension set, so you get one number written to each order line. If we use the same example as above, that’s one dimension set ID for the header, one for each line, and it is stored on the existing records. No additional records are created. When you post the document, the dimension set ID is transferred in one fell swoop to the posted documents and lines. Again, no additional records. When the sales order is deleted, there are no external records to remove. Imagine the amount of disk space that saves. 

Depending on the extent to which dimensions are used, we have seen a 10-30% decrease in database size during upgrades simply due to the new dimensions management restructure. That is something to consider if you have a rapidly growing database. To see a one-terabyte database shrink to 700 gigabytes in an upgrade is a reason to celebrate.

Dimensions, Table Locks, and Slow Performance

Table locks are issued in code with the LOCKTABLE function. This prevents multiple users from writing to the same record at one time. This collision of data would create all sorts of issues in NAV, so NAV prohibits it.  When posting routines are slow, typically due to disk operations (like writing dimension records), there is a greater opportunity for a user collision to occur. When this does happen, a message is sent stating that another user has the table locked, and the operation cannot be performed. It is sort of like a revolving door. The faster it moves, the more people (or transactions, in this analogy) can enter. However, if anything slows down your revolving door (processing), your transactions are likely to hit a closed door. By using the new dimension set ID design, NAV has increased its processing speed, which provides a decreased opportunity for those user collisions to occur.

Microsoft Dynamics NAV Going Retro

Think back a few years to the introduction of NAV 2009. Microsoft did not do us any favors when they took away the ability to see what job was locking a table back in NAV 2009. Without the ability to see the issue quickly, we had to rely on SQL traces and things of a far more technical and time-consuming nature to determine the cause of the lock. Fortunately, Microsoft seems to have relented, and yes, NAV 2017 once again includes the ability to see who is causing a job to be locked.

To illustrate, I have created a lock on the Customer table. Then I have gone into a customer record, and tried to update the name.  As you already know, that is not possible with a table lock, and so the error below is given:

Dynamics NAV Table Lock Error on Customer Card
Figure 1 - Error Message on Customer Card

Now in this example, of course, I know who created the lock. However, imagine in a database of 100 active users this occurs, and perhaps even on the General Ledger Entry table. There is no easy way in versions from NAV 2009 through NAV 2016 to find the cause of the lock. Even in versions before 2009, when the lock occurs and you can find out who it is, it is a huge headache to resolve because the processing speed often makes this a recurring issue. In walks our hero, NAV 2017. 

In the NAV 2017 development client, simply choose Tools – Debugger – Database Locks.  Any, and all, locks that are currently found in the database are shown.  The image below shows just how simple it is to determine the cause of a table lock.

Dynamics NAV 2017 Database Lock Feature
Figure 2 - Dynamics NAV 2017 shows the cause of the table lock

How do you end the lock? Upgrade your old database, and not only will you have less opportunity for table locks, but you’ll decrease the size of your database immediately when those dimension records are converted to dimension set IDs. 

Contact our upgrade team today for a quick estimate of what a Dynamics NAV upgrade will cost you. They are more affordable than you may think, and the ROI is evident when you consider the loss of processing time due to table locks and slow postings. For more information on Dynamics NAV upgrades and other ways upgrading NAV may save you time and money, please visit our website. 


Microsoft Dynamics Webcasts This Week: GP time tracking; Optimize ecommerce, batch manufacturing in NAV

$
0
0

Here's what's happening on this week's live webcast schedule. Register to attend live or get access to the recorded event.

Tuesday, March 14, 2017

Achieving Time Tracking Nirvana in Microsoft Dynamics GP 12:00 PM EDT Register

Brian MaxinTime, expense and resource tracking is essential for any type of business, helping you to understand your company operations at a much higher level. From there, you can recognize where and how to...

read more

How “not” to increase the batch name

$
0
0

NAV standard, in the case of use of batch name containing numbers, after posting automatically increases the last number existing in batch name (example: Batch 1 > 2 ..AL110A > AL111A.. and so on..)

This functionality is handled “Bydesign” in NAV, if you want to “NOT increase” the number and keep the same number in the batch (example in the case of fixed batch used for example for output and consumption and related numbered machines, former assets) can modify the codeunit 23 “Item Jnl.-Post Batch”

To achieve this, you need to change this line ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”) in function HandleNonRecurringLine

Function HandleNonRecurringLine

(VAR ItemJnlLine: Record “Item Journal Line”; OldEntryType: ‘Purchase, Sale, Adjmt Positive., Negative Adjmt., Transfer, Consumption, Output,, Assembly Consumption, Output Assembly’)

Original Code
ItemJnlLine3.COPY (ItemJnlLine);
ItemJnlLine3.DELETEALL;
ItemJnlLine3.RESET;
ItemJnlLine3.SETRANGE ( “Journal Template Name”, “Journal Template Name”);
ItemJnlLine3.SETRANGE ( “Journal Batch Name”, “Journal Batch Name”);

IF NOT THEN ItemJnlLine3.FINDLAST
IF INCSTR ( “Journal Batch Name”) <> ” THEN BEGIN
ItemJnlBatch.DELETE;
ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”);
IF THEN ItemJnlBatch.INSERT;
“Journal Batch Name”: = ItemJnlBatch.Name;
END;

You can change code in this way… for example in case of Outputs Consumptions entries to post from machine from MES..
IF NOT (ItemJnlLine2. “Entry Type” IN [ItemJnlLine2. “Entry Type” :: Consumption, ItemJnlLine2. “Entry Type” :: Output]) THEN
..
//ItemJnlBatch.Name: = INCSTR ( “Journal Batch Name”); // OLD
ItemJnlBatch.Name: = “Journal Batch Name”; // NEW, maintain old batch name, don’t use INCRSTR statement
..

Nice post here on Mibuso about this issue.
Journal batch names post
http://forum.mibuso.com/discussion/44485/journal-batch-names


How to Track Cash Flow in Dynamics NAV 2017

$
0
0

How to Track Cash Flow in Dynamics NAV

Are you looking for a better way to analyze the cash in your organization? Then take a look at the Cash Flow features available in Microsoft Dynamics NAV 2017.

The Cash Flow module in Dynamics NAV allows you to analyze your cash position, integrating data from the following sources:

  • General Ledger account balances
  • General Ledger budgets
  • Receivables transactions
  • Purchasing transactions
  • Planned incomes and expenses

This illustration outlines the process:

Dynamics NAV 2017 cash flow feature

Within the Cash Flow modules, a cash flow chart of accounts is configured and mapped to your General Ledger chart of accounts, allowing the cash flow process to combine like accounts from the General Ledger.

A second set of payment terms can be assigned to customers and vendors to reflect the actual anticipated payment terms of these transaction.  For planned transactions, both the General Ledger Budget or manually created cash flow transactions can be created and incorporated into the Cash Flow Forecast.

Dynamics NAV cash flow forecast

Once the determination is made as to what types of transactions to include, a suggested set of transactions is identified and can be updated or removed prior to updating the cash flow forecast.

Dynamics NAV 2017 cash flow feature

After the transactions are registered in Dynamics NAV, they can be used in reports or displayed in the role center in a chart.

Dynamics NAV cash flow chart

Summit EMEA 2017: Practical Power BI for analysis and reporting in Dynamics NAV

$
0
0

Magnus RamfeltSwedish consultancy Ekonomi KlaraPapper trades in business intelligence, accounting, and payroll. It uses Microsoft Power BI in its own business and to help clients measure accounting and payroll performance, and the company will share its best practices at NAVUG Summit EMEA 2017.

Magnus Ramfelt is a partner with Ekonomi KlaraPapper, and the founder of the two-year-old Dynamics NAV user group in Sweden. He also manages both KlaraPapper's own NAV and Power BI installations. He says that being a mid-sized business of about 60 consultants, &quo...

read more

Introducing Power BI

$
0
0
Power BI is a Business Intelligence solution provided by Microsoft. It consists of a Windows desktop application called Power BI Desktop; online Software as a Service (SaaS) called the Power BI service;...(read more)

How to create Dynamics NAV Inventory list report with Simplanova Report Wizard

$
0
0
Simplanova Report Wizard (SRW) allows you to quickly and easily build Dynamics NAV reports. You don’t need to know all Dynamics NAV report peculiarities and workarounds to get started. Users say it is...(read more)

Dynamics ERP and CRM Continue Together

$
0
0
I didn’t write a blog for a while, but these few days I’m on eXtreme 365 conference and I decided to share some observation. For some time, since there is a Dynamics 365 product family, we created a closer...(read more)

Benefits of Power BI using Jet Enterprise as a Business Intelligence Solution

$
0
0

Business Intelligence Options

Jet Enterprise Powers Microsoft Power BI for Business Intelligence

Business changes fast. To get ahead of the changes, you need to have insight into trends within your company and be able to predict changes on the horizon. You need access to a powerful, reliable business intelligence solution. However, it is often difficult to determine which business intelligence solution is best for your needs. There are many products in the market. This blog will look at the benefits of Power BI using Jet Enterprise as a business intelligence solution.

Jet Enterprise as Business Intelligence Solution

The steep learning curve to get up and running with a business intelligence system is often a major obstacle to success. However, with Jet Enterprise, you already have the majority of the measures you will need defined. There is no guesswork of finding the tables and auditing the results. The source table for some of the above measures is the Posted Sales Transactions table (see figure 1).  Looking below (figure 2) you can see the use of multiple root table sources. This means that getting started with Power BI and Jet Enterprise does not take weeks, but days. Additionally, most dimensions that are commonly needed are already defined and properly linked.

Screen shot of Jet Enterprise pre-built data cubes

Figure 1 – Jet Enterprise Pre-built Data Cubes

 

Jet Enterprise Data Manager screen shot showing tables used
Figure 2 –Jet Enterprise Data Manager Showing Tables Used for Sales Measures

Using the Jet Data Manager to create and manage your data warehouse and cube solution will ensure that your project is always cared for. With data lineage, impact analysis tools, incremental loading, documentation and other tools, data warehouse automation tools are quickly becoming an industry standard for SSAS management for small to medium businesses. 

Connecting Power BI to the Jet environment is the same as connecting to any other SQL or cube data source. To connect, open Power BI Desktop, select the analysis service or SQL environment and connect.  Using Power BI with a source of a predefined cube is ideal for self-service reporting.  In the below image I clicked on the Bar Chart and then clicked Year and Amount. This displayed the amounts over time. Using Power BI is that simple. Adding extra measures or dimensions is also quite easy with Jet Enterprise.

Power BI connected to Jet Reports Enterprise pre-defined sales data cube
Figure 3 – Power BI Connected to Jet Enterprise Pre-defined Sales Cube

Jet Enterprise and Power BI Dashboard Examples

Using Jet Enterprise and Power BI, we were able to create and setup the dashboards below in a single day. Click the links below to view each example dashboard:

Do you have business data you’d like to bring to life and do not know how to begin? Do you want to know how you can use Power BI and Jet Enterprise as a business intelligence solution to help grow your company? ArcherPoint can help. Contact one of our Power BI consultants today to get started. 

Microsoft Dynamics 365 readiness guide for consultants

$
0
0
Microsoft Dynamics 365 marks an exciting new turn in the ERP and CRM world. Because of the product’s new positioning, Dynamics 365 readiness can involve a lot of work. Microsoft are now actively promoting...(read more)

Dynamics 365 for Financials: No New Dynamics NAV

$
0
0
In November last year, Microsoft launched its new cloud-based solution Dynamics 365 on the North American market. Release in four more European countries is planned for this year. The Business Edition...(read more)

4 New Dynamics NAV 2017 Features You’ll Actually Love

Progressus Software a Project Management Solution

$
0
0




Progressus is next-generation Professional Services Automation and ERP software, mobile-enabled and architected for the intelligent cloud. Progressus provides all the capabilities needed to manage professional services and project-based businesses of any size – operating in any geography. Functionality spans all the important processes in your firm – resource management, project management, sales and marketing, human capital management and financial management to give you unparalleled insight and control of all of your critical business functions. Built on Microsoft Dynamics NAV, Progressus is constructed for cloud deployment, and provides role-based clients optimized for any browser or mobile device.
Microsoft Dynamics NAV is a global business management solution that provides small and midsize organizations greater control over their financials and can simplify all aspects of their company from professional services and project management to supply chain and manufacturing. It’s quick to implement and easy to use, with the power to support your growth ambition. Microsoft Dynamics NAV is available in the cloud on Microsoft Azure, and offers deep interoperability with Office 365.
Progressus adds advanced project accounting, project management and resource management to the powerful financial management functionality of Microsoft Dynamics NAV to provide the most advanced business management solution for professional services and project-based businesses. Progressus offers unique and powerful functionality in these areas:
·         Quick Project Setup
·         Project Budgeting
·         Resource Management
·         Project Monitoring and Analyzing
·         Project Cost Tracking
·         Remote Project Time & Expense Entry & Approval
·         Project Invoicing
·         Project Reporting, Analytics & Forecasting

By leveraging Dynamics NAV as platform, Progressus adds powerful project management to the vast ERP capabilities of NAV without costly or complex integration, including robust Service Management, Supply Chain Management, Manufacturing or Sales and Marketing Management.
“Plumbline Consulting has extensive experience creating solutions for project-based and professional services organizations, and we’re excited to have them bring that expertise to a new offering built on Microsoft Dynamics NAV,” said Paul White, General Manager of Microsoft Dynamics. “We’re also very pleased to announce that Progressus will be available in the cloud on Microsoft Azure through the Microsoft Dynamics NAV managed service for partners.”
“Plumbline Consulting’s depth and breadth of project expertise has allowed us to expand our growing base of solutions to project-based companies. The Progressus Software solution will provide valuable tools to project managers and employees worldwide”, said Joseph Longo, President of Plumbline Consulting.
About Plumbline Consulting
The Plumbline Consulting team has over 30 years history in implementing project-based ERP solutions. Plumbline provides software engineering and consulting services for Microsoft, Microsoft Dynamics® Channel Partners and Microsoft Independent Software Vendors (ISVs). Plumbline offers software development, application support, technology and business process consulting, with a focus on delivering excellence and building lasting relationships. Plumbline also provides Dynamics SL (formerly known as Solomon Software) Product Management, Development and Support services for Microsoft Corporation. The company is headquartered in Findlay, Ohio. More information about Plumbline Consulting can be found at http://www.plumblineconsulting.com.

Email: info@plumblineconsulting.com
Website: 
http://www.progressussoftware.com
YouTube site: 
https://www.youtube.com/channel/UCEJ_7z4gDGr1iz_pGVvAoTw



Upgrade Tips & Tricks Teil 3

$
0
0

Heute gibt es den ersten deutschsprachigen Blogartikel zum Thema Microsoft Dynamics NAV Upgrade Tipps & Tricks.

Die vorherigen beiden Blogartikel zum Thema Upgrade Tipps & Tricks 1 und 2 finden Sie in Englisch auf dem NAV Team Blog.

Best Practices Tips and Tricks for Upgrading to Dynamics NAV 2013 R2 or Dynamics NAV 2015

Best Practices Tips and Tricks for Upgrading to Dynamics NAV 2013 R2 or Dynamics NAV 2015 Part 2

Der dritte Teil beschreibt eine Problematik in NAV 2017, häufiger aufzutreten scheint.

‚UPG Item ist nicht vorhanden‘:

SessionId    : xx
CodeunitId   : 104xxx (abhängig von Version)
FunctionName : UpdateItem
CompanyName  : CRONUSxxxx
StartTime    : xxxxx
Duration     :
State        : FailedPendingResume
Error        : The UPG Item does not exist. Identification fields and values: No.=’xxx’

Für Entwickler, die sich mit Upgrade Szenarien beschäftigen, kennen diese Fehlermeldung sicherlich und haben diese schon beheben müssen. Dennoch bleibt die Frage des Warum:

  • Was bedeutet der Fehler?
  • Was kann ich diesen lösen?

Was ist ‚UPG ITem‘ überhaupt?

Alle Tabellen die mit dem Namen UPG* anfangen, sind Hilfstabellen, die in der Upgrade Tool Kit zu finden sind. Sie helfen der Upgrade Logik und den Upgrade Codeunit als temporäre Speicher für das Upgrade von Daten und Strukturen.

UPG Tabellen sind ein Teil der Upgrade FOBs. UPG Tabellen sind Lokalisierungsabhängig.

Was bedeutet ‚UPG Item ist nicht vorhanden?

Wenn man die Upgrade Tool Kit Objekte importiert, werden alle UPG Tabellen automatisch erstellt. Z.B. die Objekte in ‚Upgrade900100.DE.fob‘:

up1

up2

Das bedeutet, auf dem SQL Server ist die Tabelle nun vorhanden:

up3

Was bedeutet nun der Fehler?

Der Fehler erscheint, wenn wir die Schema Sync. ausführen, nachdem wir das Upgrade Toolkit importiert haben. Der Fehler sagt die Tabelle UPG Item ist nicht vorhanden, aber wir können mit Sicherheit sagen, dass die Tabelle vorhanden ist, da wir diese auf dem SQL Server sehen können.

Der Fehler bedeutet, dass die Tabelle physikalisch vorhanden ist, aber keine Datensätze enthält.

up4

Warum sind Daten in der Tabelle wichtig und wieso könnten diese Tabelle geleert worden sein?

Die Daten von T104092 sind für die Upgrade Prozeduren wichtig, die Erklärung finden wir in CU 104075 als Beispiel.

Cu 104075:

[TableSyncSetup] GetTableSyncSetupW1(VAR TableSynchSetup : Record “Table Synch. Setup”)

// The purpose of this method is to define how old and new tables will be available for dataupgrade
// The method is called at a point in time where schema changes have not yet been synchronized to
// the database so tables except virtual tables cannot be accessed

// TableSynchSetup.”Table ID”:
// Id of the table with schema changes (i.e the modified table).

// TableSynchSetup.”Upgrade Table ID”:
// Id of table where old data will be available in case the selected TableSynchSetup.Mode option is one of Copy or Move , otherwise 0

// TableSynchSetup.Mode:
// An option indicating how the data will be handled during synchronization
// Check: Synchronize without saving data in the upgrade table, fails if there is data in the modified field/table
// Copy: Synchronize with saving data in the upgrade table, the modified table contains data in matching fields
// Move: Synchronize with moving the data in the upgrade table,the changed table is empty; the upgrade logic is handled only by application code
// Force: Synchronize without saving data in the upgrade table, disregard if there is data in the modified field/table

// Examples:
// DataUpgradeMgt.SetTableSyncSetup(DATABASE::”Sales Header”,DATABASE::”UPG Sales Header”,TableSynchSetup.Mode::Copy);
…………
DataUpgradeMgt.SetTableSyncSetup(DATABASE::Item,DATABASE::Table104092,TableSynchSetup.Mode::Copy);
…………

Das bedeutet, für die Schema Sync. spielt es eine Rolle, ob die Tabelle voll oder leer bleibt.

Warum genau ist das so?

Wenn wir die Upgrade Schritte von diesem KB folgen: https://msdn.microsoft.com/en-us/dynamics-nav/upgrading-the-data

Step 10:

##

Task 10: Run the schema synchronization to synchronize the new tables

Similar to task 8, to publish the data schema changes of the newly imported tables to the SQL tables, run the Sync. Schema For All Tables – With Validation option from the development environment or run the Sync-NavTenant cmdlet from the Microsoft Dynamics NAV 2017 Administration Shell.

##

Es ist klar beschrieben, dass die Schema Sync. mit Validierung ausgeführt werden sollte. Oft ist das aber die Ursache des Fehlers.

Im nächsten Schritt führt man ein Sync.– mode Checkonly aus, um herauszufinden, was genaue im Hintergrund passiert.

…..Voila!

PS C:\Windows\system32> Sync-NAVTenant DynamicsNav100 -Mode CheckOnly

Sync-NAVTenant : The schema synchronization may result in deleted data. The following destructive changes were detected:

 Table: 18, Customer Field: 5001900, No. Entries for Avis: Deleted Field: 5055250, Liq. Payment Terms Code: Deleted Field: 5157970, Electronic Document Dispatch: Deleted Table: 23, Vendor Field: 5001900, No. Entries for Avis: Deleted Field: 5001901, Direction Code: Deleted Field: 5001902, Payment Type: Deleted Field: 5055250, Liq. Payment Terms Code: Deleted Field: 5157970, Electronic Document Dispatch: Deleted Table: 38, Purchase Header Field: 99008500, Date Received: Deleted Field: 99008501, Time Received: Deleted Field: 99008504, BizTalk Purchase Quote: Deleted Field: 99008505, BizTalk Purch. Order Cnfmn.: Deleted Field: 99008506, BizTalk Purchase Invoice: Deleted Field: 99008507, BizTalk Purchase Receipt: Deleted Field: 99008508, BizTalk Purchase Credit Memo: Deleted Field: 99008509, Date Sent: Deleted Field: 99008510, Time Sent: Deleted Field: 99008511, BizTalk Request for Purch. Qte: Deleted Field: 99008512, BizTalk Purchase Order: Deleted Field: 99008520, Vendor Quote No.: Deleted Field: 99008521, BizTalk Document Sent: Deleted Table: 79, Company Information Field: 50000, Ort für Signatur: Length reduced Field: 50001, GSF: Length reduced Field: 50002, HRB: Length reduced Field: 60003, IBAN 2: Length reduced Field: 60008, IBAN 3: Length reduced Field: 60013, IBAN 4: Length reduced Field: 70300, Path scanned Purch. Doc.: Length reduced Table: 91, User Setup Field: 5310951, CrefoDefaultCustRefConsumer: Length reduced Table: 110, Sales Shipment Header Field: 5900, Service Mgt. Document: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 99008509, Date Sent: Deleted Field: 99008510, Time Sent: Deleted Field: 99008515, BizTalk Shipment Notification: Deleted Field: 99008519, Customer Order No.: Deleted Field: 99008521, BizTalk Document Sent: Deleted Table: 120, Purch. Rcpt. Header Field: 99008500, Date Received: Deleted Field: 99008501, Time Received: Deleted Field: 99008507, BizTalk Purchase Receipt: Deleted Table: 204, Unit of Measure Field: 60000, Inventory Unit PV: Deleted Table: 295, Reminder Header Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Table: 297, Issued Reminder Header Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Table: 5107, Sales Header Archive Field: 5158202, Archiv DocID: Length reduced Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Field: 99008500, Date Received: Deleted Field: 99008501, Time Received: Deleted Field: 99008502, BizTalk Request for Sales Qte.: Deleted Field: 99008503, BizTalk Sales Order: Deleted Field: 99008509, Date Sent: Deleted Field: 99008510, Time Sent: Deleted Field: 99008513, BizTalk Sales Quote: Deleted Field: 99008514, BizTalk Sales Order Cnfmn.: Deleted Field: 99008518, Customer Quote No.: Deleted Field: 99008519, Customer Order No.: Deleted Field: 99008521, BizTalk Document Sent: Deleted Table: 5109, Purchase Header Archive Field: 99008500, Date Received: Deleted Field: 99008501, Time Received: Deleted Field: 99008504, BizTalk Purchase Quote: Deleted Field: 99008505, BizTalk Purch. Order Cnfmn.: Deleted Field: 99008506, BizTalk Purchase Invoice: Deleted Field: 99008507, BizTalk Purchase Receipt: Deleted Field: 99008508, BizTalk Purchase Credit Memo: Deleted Field: 99008509, Date Sent: Deleted Field: 99008510, Time Sent: Deleted Field: 99008511, BizTalk Request for Purch. Qte: Deleted Field: 99008512, BizTalk Purchase Order: Deleted Field: 99008520, Vendor Quote No.: Deleted Field: 99008521, BizTalk Document Sent: Deleted Table: 5900, Service Header Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Table: 5992, Service Invoice Header Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Table: 5994, Service Cr.Memo Header Field: 5157970, Electronic Document Dispatch: Deleted Field: 5157971, Bill-to E-Mail: Deleted Field: 5157972, Send As Copy: Deleted Table: 50001, Customizing Setup Field: 1040, Shipping Date: Deleted Field: 1050, Edit Post. Groups in Gen. Jnl.: Deleted Table: 51000, External Entries Setup Field: 1, Key: Data type changed Table: 75400, Mail Batch Field: 50000, Sofortversand: Deleted Field: 50001, mit Signatur: Deleted Field: 50003, Erstell-Datum: Deleted Field: 50004, Sonderbehandlung bei info@: Deleted Table: 75401, Mail Batch Line Field: 30, CI Name: Length reduced Field: 50000, Segment No.: Deleted Field: 50001, Salesperson Code: Deleted Field: 50002, Suchbegriff Unternehmen: Deleted Field: 50003, Contact Company No.: Deleted Field: 50004, zHd: Deleted Table: 75402, MailIT Setup Field: 50000, Quote Report ID: Deleted Field: 50002, Order Report ID: Deleted Field: 50004, Abnahme Report ID: Deleted Field: 50006, Bestellung Report ID: Deleted Table: 75403, MailIT Report Field: 1, ID: Data type changed Field: 3, User ID: Deleted Field: 2, Caption: Deleted Table: 5157823, Reserved 5157823 Field: 1, Dummy: Data type changed Table: 5157825, Reserved 5157825 Field: 1, Dummy: Removed from primary key - Data type changed Table: 5157917, Reserved 5157917 Field: 1, Dummy: Data type changed Table: 5158202, Document Archive Setup Field: 22, Sales Process Nos.: Length reduced Field: 23, Purchase Process Nos.: Length reduced Table: 5158221, Invoice Monitor Setup Field: 2, Default Journal Template Name: Length reduced Field: 3, Default Journal Batch Name: Length reduced Table: 5158225, DropZone Lookup Values Field: 1, Archive Document Type: Data type changed Field: 3, Document Type: Data type changed Field: 6, Value: Deleted Field: 5, Source Type: Deleted

Was wäre der nächste Schritt? Einfach Sync. mit Force oder? BITTE NICHT…. Das wäre ein Fehler!

Das ist genaue was wir nicht wünschen, da wir nicht genaue wissen, welche Daten mit der Force Option gelöscht werden könnten.

Sogar wenn die Tabelle Item, nicht in dieser List ist, weiß man nicht genaue, was mit der Force Option genaue gelöscht wird, Grund sind Tabellenrelationen zwischen den Tabellen in der obigen Liste und andere Tabellen die bestehen und ggf. und angepasst wurden.

Was ist nun zu tun?

Bitte nehmen Sie Abstand von einem Sync. mit der Option Force, wenn es nicht wirklich sein muss.

Diesen Fehlern sollten erst behoben werden, dann können wir die Schema Sync. mit Validierung weiter ausführen.

Wie können wir den Fehler beheben?

1. Entweder schreibt man eigene Upgrade Codeunit, wie zu sehen in der Codeunit 104075, um zu erklären, was NAV mit den gelöschten Feldern tun soll. Das Upgrade Codeunit Konzept haben wir erst ab NAV 2015 präsentiert. Eine Erklärung mit Beispiel finde Sie z.B. hier: http://vjeko.com/upgrade-codeunits-in-nav-2015/ Und auch als Video: https://community.dynamics.com/nav/b/navvideos/archive/2014/11/05/how-do-i-synchronize-database-schema-using-upgrade-codeunits-in-microsoft-dynamics-nav-2015

 

So kann man als Beispiel die CU 104xxx anpassen:

DataUpgradeMgt.SetTableSyncSetup(DATABASE::"G/L Account", DATABASE::"MyUPG G/L Account",TableSynchSetup.Mode::Copy);
DataUpgradeMgt.SetTableSyncSetup(DATABASE::Customer, DATABASE::"MyUPG Customer",TableSynchSetup.Mode::Copy);
DataUpgradeMgt.SetTableSyncSetup(DATABASE::Vendor, DATABASE::"MyUPG Vendor",TableSynchSetup.Mode::Copy);

Wo “MyUPGxxx” Tabelle, ist die wo wir die alten Strukturen und Daten temporär sichern möchten, der Rest von der Anpassung ist in der oben genannten Artikel erklärt.

2. Eine weitere Möglichkeit wäre ein einfachere Merge mit Cronus Objekte aus der neuen Version

Einfach die alten Objekte z.b. Cutomer und Vendor Tabellen nehmen und einen Compare-Merge mit selben Tabelle aus der neue Version durchführen.

Danach exportiert man die Merge Ergebnisse als fob aus der neuen Version.

Wenn nun die FOB importiert wurde, sollte die Schema Sync mit Validierung einwandfrei ausgeführt werden können und nur dann es ist garantiert, dass dieser Fehler nicht mehr auftaucht.

up5

up6

up7

Das Upgrade ist nun erfolgreich ausgeführt worden:

up8

 

Mit freundlichen Grüßen,

Abdelrahman Erlebach
Microsoft Dynamics Germany

Special Thanks for Duilio Tacconi for his great contribution in the area of schema Sync. and data Upgrade.

Disclaimer Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the limitation and disclaimer set out below may not apply. ACCEPTANCE AND DISCLAIMER OF WARRANTY The software contained in this communication is provided to the licensee “as is” without warranty of any kind. The entire risk as to the results, usefulness and performance of the software is assumed by the licensee. Microsoft disclaims all warranties, either express or implied, including but not limited to, implied warranties or merchantability, fitness for a particular purpose, correspondence to description, title and non-infringement. Further, Microsoft specifically disclaims any express or implied warranties regarding lack of viruses, accuracy or completeness of responses, results, lack of negligence, and lack of workmanlike effort, for the software. LIMITATION OF LIABILITY In no event shall Microsoft be liable for any direct, consequential, indirect, incidental, or special damages whatsoever, including without limitation, damages for loss of business profits, business interruption, loss of business information, and the like, arising out of the performance, use if, or inability to use, all or part of either the software, even if Microsoft has been advised of the possibility of such damages.

ArcherPoint Dynamics Developer Digest - vol 133

$
0
0

ArcherPoint Dynamics NAV Developer Digest - vol 133Developer Dude

The NAV community, including the ArcherPoint technical staff—is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.

How to Configure the Excel Add-In in MS Dynamics NAV

Microsoft Dynamics shares on their YouTube channel a demonstration of how to configure the Excel Add-In in Microsoft Dynamics 2017. It includes the prerequisites, creating the app in Azure management portal, granting access to the app, OAuth2 configuration, and the NAV server configuration.

Dynamics NAV 2017: Update Item Inventory from Item Card

Saurav asks if the ability in NAV 2017 to update item inventory from the item card is a feature or a bug in his latest blog. Check out his post and weigh in from your customer’s point of view whether this is a feature or a bug.

Dynamics ERP by the Numbers

Our friends at ERPSoftwareBlog.com share how many companies use the various Microsoft Dynamics ERP products, at least the most recent numbers available. NAV wins!

Object Metadata Table Lock when Compiling Objects

Tom Hunt shares an issue when trying to do an object compile with only 10 tables. The error message is below, stating, “The Object Metadata table cannot be changed because it is locked by another user. Wait until the user is finished and then try again."

MS Dynamics NAV Development Environment Error: Object Metadata table cannot be changed
Figure 1 - Dynamics NAV Development Environment Error: Metadata table locked

The error states that this can be caused by one of the following tasks:

  • Objects are being compiled.
  • Table schema is synchronizing.
  • Objects are being imported.

Tom explains, “I’m the only user in the database. I just restarted the SQL Server service and all the NAV service tiers, so I'm not quite certain what would be causing this. Does anyone have any ideas?”

Suresh asks Tom which version, and suggests if in a new version to try sync-schema from Tools.

Tom replied that he is working in NAV 2015 and wasn’t aware of the sync-schema tool. Unfortunately, the sync-schema, nor turning off all service tiers, nor restarting SQL resolved the issue.

Bill W suggests, “You could try to see what has the lock and is blocking. I use this method, from the Using SQL Server Extended Events to Produce a Blocked Process Report blog, which is more accurate than checking activity monitor.

That SQL Command turns on the logging. Instead of using the report they setup, just open up SQL Profiler and then pick the Blocked Process Report. That should tell you what has a lock on the table.

Blocked Process Report from SQL Profiler showing what is locking the table
Figure 2 - SQL Profiler's Blocked Process Report

SSRS versus RDLC Reports

Michael Heydasch shares that he recently wrote SSRS (SQL Server Reporting Services) reports for a client that needed visibility into more than one company. In doing so he discovered that SSRS is true RDL (Report Description Language) that includes the query needed to gather a dataset, whereas Dynamics NAV is RDLC (Report Definition Language Client-side) and the dataset is expected to be provided.

Leadership Lines

For those practicing Agile in any capacity, Jon Long reminds us of the Manifesto for Agile Software Development:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center.

And, if you are interested in NAV development, be sure to see our collection of NAV Development Blogs.

Blog Tags: 

Idle Session Management

$
0
0
To be released on 10/10/2016! With Idle Session Management inside NAV, you can specify Idle Client Timeout, Total Sessions for each user, and allocate Concurrent Client Access Licenses (CCALs) to group...(read more)

Query and Excel Report

$
0
0
As you know, Microsoft Excel has tremendous capabilities such as Formula, Chart, Power Pivot, Slicer, and Condition Format … help you build stunning dashboards and reports. Now with our solution...(read more)

Microsoft Dynamics Partner Roundup: Warehousing for Dynamics 365; High-tech sales ops; D365/QuickBooks integration; Worldwide consumer attributes

$
0
0

In this week's Microsoft Dynamics Partner News Roundup:

  • Enterprise Data Warehousing Solution by mcaConnect Now Available for Microsoft Dynamics 365 for Operations
  • Tensoft Launches SaaS Offering for Technology Companies with Design Win Models
  • DBSync Cloud Workflow IPaaS now Available at Microsoft AppSource to Help Companies Seamlessly Integrate Key Business Apps
  • Versium Expands LifeData to Include Business and Consumer Attributes from More Than 100 Countries to Power Predictive Analytics & Data Enrichment across the Globe

Enterprise Data Warehousing Solution by mcaConnect Now Available for Microsoft Dynamics 365 for Operations

m...

read more

Friends Across the Pond - Summit EMEA is Coming to a City Near You!

$
0
0

Looking for a peer-to-peer focused conference dedicated to Microsoft Dynamics NAV end user education and networking? Look no further, join us in Amsterdam 4-6 April at Summit EMEA 2017.

Summit EMEA 2017 is the premier conference for Microsoft Dynamics NAV users in EMEA countries. In a days' travel, you'll have access to connect directly with Microsoft team member, fellow end-users in similar roles and industries, and subject matter experts. These relationships will propel you and your organization forward with your product software investment.

Discover what Summit EMEA 2017 has to offer:

REGISTER TODAY. Join your peers in Amsterdam next month.

Plataan.tv

$
0
0
Word nog sneller ERP, CRM, BI, Project of IT Management specialist! On -en offline leren op onze vernieuwde www.plataan.tv website ! What do you want to learn today? Op Plataan.tv vind je nu ook onze offline trainingen, trainingen die je bij ons ...read more
Viewing all 7890 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>