Version "Vendor invoice workflow - v5" already exists. Import has been canceled AX 2012/ D365F&O

 I was getting the bellow error while trying to import the workflow configuration from DEV to UAT.

Version "Vendor invoice workflow - v5" already exists. Import has been canceled.

Usually you see this error when the work configuration is having the same version number. 

Ex: 5.0.0.0

Solution:

--------------

-> Open the workflow configuration file(XML) in notepad/notepad++

-> Search for "versionIdMajor" attribute/field in the XML. Usually, you find it in the end of the XML file.

-> Update the versionid number to higher number.

Ex: In  my case the previous number was 5 and I updated it to 6.

That's it

@Rahul

D365 Finance VSTS/ azure devops DB sync fails / [error]SYNCENGINE(0,0): Error Number: -2,State:0,Class:11/ C:\DynamicsSDK\Metadata\SyncEngine.proj] Database synchronization failed

 While working with the D365 F&O build server, we suddenly started to get the timeout error on the database synchronization step. Checking the logs on the azure dev ops pointed out that, db sync was not able to complete the login phase for the sql server. 

 

This was odd, as the builds have been working fine until this point. This was a wild goose chase to check the settings of the sql server, hosts file, testing pings etc …

 

Build failed:

 

This started happening after we took 10.0.14 quality update, or it was co-incidence – we are not sure yet.

Resolution:

 

It came down to the “Auto close” was set to “True”, after changing that to “False”, we can see that now builds are getting done successfully.

Connect to Cloud hosted build server and open SSMS - Sql server management studio and connect to AxDB.

If in case AxDB in recovery mode run the below query to set it normal.

ALTER DATABASE AxDBSET MULTI_USER;
GO

Now, right click on AxDB and go to properties -> Go to potions and set Auto close false.

or you can run below query to set auto close off.

ALTER DATABASE [AxDB] SET AUTO_CLOSE OFF;

@Rahul

for more details please refer below link.

https://rizworks.wordpress.com/2020/02/23/d365-fo-dbsync-error-errorsyncengine00-error-number-2state0class11/

Trial balance is not matching with all transactions in dynamics ax 2012 or Dynamics 365 finance

 This is a very common problem that some times the trial balance debit/credit would not match with all transactions. Usually, you see this issue during year end closing. 

The same thing happed to me as well. I checked all the reports ex: ledger transactions and dimension statement reporta and all the transactions looks correct but still not matching with the trial balance.

Solution : Rebuild financial dimension set solved my problem. 

@Rahul

I found below post and this will give you more details about the issue. Hope this helps! 

https://community.dynamics.com/365/financeandoperations/b/dynamics-365-finance-blog/posts/best-practices-for-updating-financial-dimension-set-dimension-sets

Financial dimension sets allow you to create a combination of the main account and financial dimensions, and the order of them for analyzing balances on the Trial balance list page and various reports.

 

 

When you first create a financial dimension set, you must select Create balances before it can be selected for analysis. Once the balances are created, they can be selected in various report and inquiry screens.

 

There are two options available on the Financial dimension sets for balances once they are created.

• Update balances – update will take any records that have not been added to the balances yet and update them. This is a net new update.

• Rebuild balances – rebuild will completely clear the balance and new records and recreate the balance from the beginning of time.

 

You can schedule periodic updates for the balances, but also note that some reports or inquiries will run the update during processing. For example, on the Trial balance list page, when you click Update, it runs an Update balances for that financial dimension set.

 

So how do you know if you should schedule updates or rebuilds? Let’s cover some best practices for this process:

 

1. Only create the financial dimension sets you need and use. Otherwise you are just using up time and resources to rebuild and/or initialize something that is unnecessary. For example, if you are never going to analyze the combination of Main account and cost center, do not create it as a Financial dimension combination. Processes such as Year end close or consolidation rebuild all financial dimension sets during their processing, and this can add significant time to the process.

2. Rebuild balances only if needed, such as a last attempt at troubleshooting if you don’t think the balance is right or are missing a transaction in the balance.

3. Schedule Update balances periodically, as if you do large postings or imports, so that the new records are committed to the balance. It is best to schedule this during off-peak hours.

4. It is not recommended to schedule Rebuild balances unless you identify a situation and feel it needs to become a periodic process. If you must schedule a rebuild, it is highly recommended to do it infrequently (perhaps monthly), and at a time when there is no other processing on the system

The SMTP server requires a secure connection or the client was not authenticated. The server response was: Authentication required in Dynamics 365 Finance / Dynamics AX

 I was getting the below error while try to send a test email through email parameters after updating SMTP details.

The SMTP server requires a secure connection or the client was not authenticated. The server response was: Authentication required

Solution

------------------

-> After updating the SMTP detail refresh the application page and try again

-> If the above steps does not work, login with send as email address (ex: noreply@abc.com) and update the SMTP details and send a test email.