There seems to be limited information on how the "Send email receipts" functionality works.  This blog is intended to help provide the basic information and links on how to configure and send email receipts for EPOS transactions.

To get started, you will first need to configure a SMTP server to send the emails.  The link below will take you to the TechNet article that walks you through the steps to configure this.

Configure email functionality in Microsoft Dynamics AX
https://technet.microsoft.com/en-us/library/aa834374.aspx

You will then need to configure the email receipts settings in the Retail.  There are 3 options for how receipts will be printed/sent: POS, e-mail, or both.  You can set these to be specific to a Customer or in the Retail parameters.  The Retail parameters setting will be used when you ring up a transaction at the EPOS without a customer.  See the TechNet link below for details on setting these configurations.

Set up email receipts
https://technet.microsoft.com/en-us/library/hh597117.aspx?f=255&MSPPError=-2147217396

Set default options for email receipts
     1. Click Retail > Setup > Parameters > Retail parameters.
     2. Click the Posting tab, and then under Email receipt, in the Receipt option field, select an option as the default:
          ◦ POS – Print receipts from the point-of-sale register.
          ◦ E-mail – Send receipts to customers in email messages.
          ◦ Both – Print receipts from the point-of-sale register and send receipts to customers in email messages.
     3. In the Subject field, enter the text that appears by default in the subject line of a receipt that is sent as an email message.
     4. In the File name field, enter the file name of the recipient’s email attachment. Do not include the file extension.

Set email receipt options for a customer
     1. Click Accounts receivable > Common > Customers > All customers.
     2. On the All customers list page, select a customer, and then, on the Customer tab, in the Maintain group, click Edit.
     3. In the Customers form, on the Retail FastTab, select an option in the Receipt option field:
          ◦ POS – The customer will receive only printed receipts. The printed receipt is generated from the point-of-sale register.
          ◦ E-mail – The customer will receive only email receipts.
          ◦ Both – The customer will receive both a printed receipt and an email receipt.
     4. In the Receipt email field, enter the customer’s email address if you selected either E-mail or Both in the Receipt option field.

Create body text for the email message
     1. Click Accounts receivable > Setup > Forms > Form notes.
     2. Click New to create a new form note, and then in the Form field, select Retail Headquarters Receipt, and specify a language.
     3. On the Form note FastTab, enter the text that you want for the body of the email message.

Depending on the settings that you configured, you will need to run the respective Distribution schedule jobs to sync these changes to POS. 
     1. 1010 - Customer
     2. 1110 - Global configuration

When you launch POS and process a transaction for a customer with the option to email the receipt, you will be prompted to enter the "E-mail address for receipt".  This does perform a quick validation on the entered text to ensure it is in an email address format.

Run the P-job to sync your POS transactions back to AX.  Even though the transaction is now in the RetailTransactions tables in AX, we are not able to send the receipts yet.  The RetailEmailReceipts class is looking for transactions with an RetailEntryStatus of Posted.

Generate a new statement for the store.  Perform the Calculate Statement and Post Statement processes to post POS transactions.

Now run the "Send email receipts" periodic process under Retail >> Periodic to send out the receipts to the customers as PDF attachments.  The attachments are created from a SSRS report named RetailTransactions.  If these are processed in batch, it will use the AOS to send emails from the configured SMTP server.  Be aware that if this is ran outside of batch, it will attempt to send the emails through the local computers default email client.

If we were to look in the AX database at the RETAILTRANSACTIONTABLE table, there is a RECEIPTEMAIL field with the customers associated email address and a RECEIPTEMAILSENT (only in AX database) field that indicates if the email has been sent.  RECEIPTEMAILSENT is initially set to 0 and will be set to 1 after the “Send email receipts” has successfully processed.

NOTE: The steps above are the out of box design to only send emails after the statement is posted, which would be at the end of the day for a normal business scenario.  I understand that this may not meet customer expectations as the expectation is that receipts are received within minutes of the transaction.  In order to send the emails at a higher interval outside of posting the transactions on a statement, you can customize the process by starting to look at the RetailEmailReceipts and RetailEmailReceiptSenderBatchJob Classes.

There are probably various customization options that you could use to send these emails receipts.  Feel free to let the community know your ideas by using the comments section below.

Microsoft Dynamics AX has a function to control for the deleted sales orders or deleted lines, on this post will illustrate the voided sales order function, where the deleted sales order lines are stored in another form for reference only. First this function must be activated under accounts receivable parameter. 

Accounts receivable| Setup| Accounts receivable parameters then under General go to Sales fast tab, under Setup field group, Tick the following option Mark the order as voided.  

During the sales order transaction assume that the end user after select a sales line then delete it, the deleted line is moved to Voided sales order form

Let us create a new sales order line and delete it from the header

Then go to Sales and marketing| Inquiry| History| Voided sales orders

The voiced sales order form will open, and the voided sales orders will be shown as the following screen shot

The Voided filed has two options;

• The first is Voided lines; which represents the sales order lines that have been deleted and the sales order header is not deleted
• The second is Voided; which represents the sales order that have been deleted from the header 

Go to Lines tab, which shows the voided lines.

You can press Show to show the sales order and order lines.

The change fixed asset group function is commonly used to change the fixed asset group to another group, and consider that this function will not reclassify the asset  from the accounting point of view. Changing the asset from group to another, it may use the same asset ID or rename it, and this does not generate any financial entries.

The path of change fixed asset group go to Fixed assets| Common| Fixed assets| Fixed assets
 

In order to change an asset group select an asset ID, and go to Maintain ribbon, and press Change fixed asset group
A dialog box opens to indicate the new group, and if you need to create new fixed asset number by renaming the old one. As shown in the below screen shot a dialog box opens indicate that rename the fixed asset.

There is another function to reclassify the asset group and considering the financial entries which known as Asset reclassification, this will be covered in another blog post.

On multiple occasions I have had questions or seen confusion surrounding the usage of Post Inventory in conjunction with Calculate Statement and Post Statement for keeping inventory up-to-date and posting sales transaction. 

Let's first define the purpose of each process:

Post Inventory
When running the Post Inventory, this looks for all unposted transactions that have been synced from POS to AX using the P-job.  This will reserve inventory as needed for each item in the transactions.  Normally this will update the “Physical reserved” if there is a quantity available in Physical Inventory.  If there is not enough available inventory, then the “On Order” will be updated.  To keep your on-hand inventory accurate, you should run this batch job frequently throughout the day.  NOTE: This does NOT need to be ran prior to a statement posting, this is only ran throughout the day to keep inventory numbers current.

Calculate Statement
This will find any unposted transactions based on the statement's Setup settings and assigns them to the current statement ID.  Calculating the statement does not have any additional effect on the Inventory Posting that was performed. If the Post Inventory was not performed or some items missed the last Post inventory prior to the Calculate statement, then the On order will be updated based on the quantity of items in the statement's transactions.

Post Statement 
The Post statement process will reverse the Post Inventory reservations and officially create sales orders in AX based on the statements transactions.  This will normally update the Physical Inventory quantities, even going negative if allowed by the Item model group. If the Calculate Statement captured any items outside of the Post inventory, which could normally be the case at the very end of the day just prior to posting the statement, it performs a similar check by moving any of the related On order items to Physical Inventory during the sales order creation.


Below are two basic examples using AX 2012 R3 on how inventory was affected when the above 3 processes were used to post a POS transaction.  The first one has available quantities to cover the items sold at the POS, the second one does not.  Click on the pictures to view them at a larger size.


Posting Inventory and then Posting the statement when an item has available quantities.

Starting on-hand inventory quantities for item 0008 are set at 45



A cash and carry transaction is performed at the POS for a quantity of 1 for item 0008. The P-job is ran to bring the transaction into AX.  Note that the quantities have not been affected yet.



Run the “Post inventory” operation for that store. There is now 1 in Physical Reserved and the Available Physical has been deducted by 1.



Create and calculate a statement for this store.  Once again, no change.



Post the statement.  The Physical Inventory is now updated to 44 from the 1 in Physical Reserved as a sales order was created in AX.




Posting Inventory and then Posting the statement when an item does NOT have available quantity, a movement journal is performed to make it available.

Starting on-hand inventory quantities for item 0008 is at 5.



A cash and carry transaction is performed at the POS for a quantity of 6 for item 0008.  The P-job is ran to bring the transaction into AX.  Note that the quantities have not yet been affected.



Run the “Post inventory” operation for that store.  There are now 6 in On order.



Perform an Item Movement of 10 to add an available quantity.  The Physical inventory and Available physical are updated to 15, but the On order is still at 6.



Calculate and post the statement with this transaction.  The Physical inventory and Available physical are now updated to 9.
 

I have worked with several customers in relation to defaulting prices at the Item level based on differing Product dimensions where there has been some confusion about the Sales price not defaulting in appropriately. Let's walk through an example of how Sales prices are interpreted in Sales orders from posted Trade agreements based on the Inventory dimensions that you have associated with a given item. For example, assume that you have an Item called TSHIRT that is associated with a Storage dimension group that is actively using Site\Warehouse\Location. You then have a Product Variant of Color associated with the TSHIRT, so you have a Product dimension group assigned that contains the Color Inventory dimension.

When I sell the GREEN TSHIRT out of Site 1/Warehouse 11, the Sales price should be $15.00. When I sell the YELLOW TSHIRT out of Site 1/Warehouse 11, the Sales price should be $16.00. To accomplish this scenario, I have created the following Trade agreement journal to differentiate pricing based on the Color of the TSHIRT:

However, when I enter a Sales order for the GREEN TSHIRT, the Sales price does not default in at all:

The reason why the Sales price of $15.00 is not defaulting in for the Green TSHIRT Is because the Color Product dimension group that I have assigned to my TSHIRT item does not have the For sales prices option flagged for the Color dimension:

The Inventory dimension must have the 'For sales prices' option flagged at the Dimension Group level in order for the appropriate prices to be picked up based on what you had established in your posted Trade agreement journals. As a result, if I mark the 'For sales prices' option for the Color Product dimension group that is assigned to my TSHIRT item, the $15.00 Sales Price will default in when selling the GREEN TSHIRT on a Sales Order:

 RECAP:

If you are using Trade Agreement Journals to establish defaulting Sales prices based on certain Product dimension attributes, be sure that the Dimension Groups assigned to the Item for which you are selling are configured for 'For sales prices'.

I have recently worked with partners and customers utilizing Transportation Management but without intending to use Warehouse Management. There were general concerns with this is there are functions within Transportation Management that seemingly assume that correlating Warehouse Management Setup and Configuration be intact. For example, assume that you want to utilize Rating and routing functionality in Transportation Management to generate the Bill of Lading without having to use Warehouse Management work. Consider the following processes deployed in an attempt to accomplish this scenario:

• Create a new Sales Order which contains an Item for which is Transportation Management enabled. (NOTE:  The Warehouse on the Sales Order must be one that is Warehouse Management enable. This must be the case so that the Sales Order line(s) can be added to a new Load)
• The Sales Order is saved and reserved against on-hand Inventory.
• Through the Load Planning Workbench, the Sales Order line is added to a New Load.
• From the Load Planning Workbench, the Load is then Rated and Routed using the Rating and Routing Workbench. Using the Rating and Routing Workbench, the Load is assigned to a Route.
• The Sales Order itself is then Picked and the Picking List Registration is performed.
• After the Sales Order itself is Picked, the Confirm | Outbound Shipment is performed against the Load for which the Sales Order line(s) are assigned against.

At this point in time, the expectation is that you should be able to print a Bill of Lading from the Load Planning Workbench. However, when you select to print the Bill of Lading from the Load Planning Workbench, nothing happens as the call to the SSRS report is never made. The reason why the Bill of Lading will not print using these steps is because AX expects there to be a record in the WHSSHIPMENTTABLE record tied to the Load. Because there isn't a WHSSHIPMENTTABLE record, the Bill of Lading will not print.

The concern at this point is that you'd have to go through the process of creating Warehouse Management Work and completing the Work to simply create a WHSSHIPMENTTABLE record so that a Bill of Lading could be generated. Remember, the whole idea here is that we don't want to be forced to have to complete Warehouse Management work as the idea is that we don't want to even use Warehouse Management processes.

WORKAROUND:  In order to print a Bill of Lading without having to fully utilize Warehouse Management processes, you can take an approach of:

1.  Assign a Staging location type and Final shipping location type in Warehouse Management parameters. (NOTE:  If one does not exist, you will need to simply create a Location type in Warehouse management | Setup | Warehouse setup | Location types.)\

2.  After confirming the Outbound Shipment from the Load Planning Workbench form, you simply have to click the Release | Release to Warehouse button. This will prompt an InfoLog suggesting that a Shipment record has been created. (NOTE: This action itself creates a record in WHSSHIPMENTTABLE. This does not create Work in Warehouse Management, so nothing further is needed in Warehouse Management)

3.  Because a record now exists in WHSSHIPMENTTABLE, you can successfully print the Bill of Lading without requiring additional unnecessary Warehouse Management processes/steps.

RECAP:

In order to print the Bill of Lading without requiring Warehouse Management Work be performed, you simply:

• Need a Staging location type and Final shipping location type specified in Warehouse Management Parameters.
• Need to perform Release | Release to warehouse step after Confirming Outbound Shipment.

This will allow you to print a Bill of Lading from the Load Planning Workbench.

How to get the Production Picking list to Use the delivery note layout with Batch orders in Process Industries and Production orders.

If you are creating a Production order with an outsourced purchase order for a service item and want to see the purchase order and delivery date. The ‘Use the delivery note’ is a nice option to use when starting the production order and printing the Production Picking list.
Following, I will highlight the main steps needed to view the vendor delivery note information on the Picking List.

1. You will need to create a released product with a Product type of ‘Service’.

2. You will need to make sure that you have the Approved vendor setup completed for the service item.

3. You will need to create a Route for the finished good item. When creating the route make sure to use at least two Oper. No. sequences. You will need one for the regular inventory components and a second sequence for the outsourced Service item.  If you have multiple service items with different vendors, a separate Oper. No. sequence should be used for each service item.  On the service Oper. No. sequence click the General tab then select a Route type of Vendor.

4. You will need to create a Bill of Materials (BOM) for the finished good item.  When you create the BOM for the finished good add the Service item to the BOM.  Click the General tab and under Subcontractor add a Vendor account, and under BOM Line Type select Vendor.  You will also need to match the Oper. No. to the route service sequence Oper.No. 20.

5. Next you will create the production order for finished good.

6. After the production order has been created, it should then be estimated.

7. Once it has been estimated, then you would start the production order.  When starting the production order, click the General Tab and under Picking list journal and make sure that ‘Oper. No.’ is selected for the Create journal per option.  Mark the Print picking list option.  Then click the Print options button.

8. Mark the ‘Use delivery note layout’ option.  Click the OK button in the Picking list form.  Then click the OK button in the Start form.

9. Review the component item Picking list report and then close the report.

10. The next report should then be the Service item Picking List with Vendor delivery note.

The vendor delivery note can be a very useful tool for the shipping\receiving department to plan for incoming service items and expedite them if needed.

Note: If the above steps do not produce the Vendor delivery note there are a few hotfixes depending on your version and build that will help correct the issue.

You can do a search on Lifecycle Services to find them. https://lcs.dynamics.com/

 If you do a search with $\Classes\ ProdPicklistController you may find some that can potentially help.

Recently more and more cases are popping up related to:

 "Unable to update or remove Dynamics AX components as you can’t choose any component"

These cases are to 99% related to the fact that someone deleted files from the Windows installer folder.

Please have a look at the articles like:

http://blogs.technet.com/b/joscon/archive/2012/01/18/can-you-safely-delete-files-in-the-windir-installer-directory.aspx

Snipp………………………..

So, the question usually asked is: Can I safely remove the files in this directory? The answer is flatly: No. So let's talk about why this is a bad idea.

First, it is not supported. If you remove files from this directory and have issues, you may need to reinstall the application to get back to

a good state (best the whole server) . Therefore, that would suck for both you and the engineer that needs to deliver that message.

Snap………………….

Or:

http://support.microsoft.com/en-us/kb/2667628?wa=wsignin1.0

Snip……………….

If files are missing from the Windows Installer Cache, you will have to rebuild the operating system and reinstall applications.

Microsoft support engineers cannot help you recover missing files from the Windows Installer cache.

Snap……………….

If this happened in a Productive environment you can imagine how bad this is.

Our recommendation to not delete anything from this folder: c:\windows\installer folder (usually a hidden one).

This is not effecting the application as it is running.

It only comes to light if you try to update or remove the application.

If you want to know if this time bomb is ticking in your environment you have to check if the MSP file mention in the Registry for

the dynamics AX components exist in the c:\windows\installer folder (usually a hidden one).

How to:

Msi file names are easy to locate as all of them are under:

KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\

Then just Search for Dynamics under registry key above and you will find all Dynamics AX msi for installed components under LocalPackage key .

Take this file name and search for it in the

c:\windows\installer folder.

If it not exist someone or something deleted it and you need to think about rebuilding the environment or at least Application.

But keep in mind it’s not only Dynamics AX that can be effected. 

Other software is handling this the same way.

 Writer: Uwe Zimmermann <uwezim@microsoft.com>

This error message can be a little misleading as it implies that it is related to some security permissions not being configured correctly. In some cases this can be the case, however it can also be a problem with running CIL code. This can especially occur when you are going through the code upgrade steps.

There are a couple of solutions for this.

1. Try to complete a full CIL compile with errors.
2. If the full CIL fails or has errors, then uncheck the “Execute business operations in CIL”, under File > Tools > Options – in the Development tab, as below:

If you’re headed to Convergence 2015 in Atlanta, please stop by the Dynamics AX Technical Readiness Documentation booth at the Expo! We’d love to meet you and hear about your business. We’d also love to get your thoughts on the type of content that would help speed up your AX implementations!

See you in Atlanta!

Microsoft Dynamics AX 2012 R2 had introduced a new feature to automatically generate email messages to recipients based on specific events for Online Orders such as order created, picked, packed, shipped, etc.  With the addition of Call Center in AX 2012 R3, this feature was expanded to encapsulate other Retail orders.  This feature was designed to only work for Retail Sales Orders as AX queries orders in the SalesTable joined with the RetailSalesTable (see the class information at the bottom of this bog).

This feature is only applicable to orders created in the following instances:
AX 2012 R2 for Retail - Online Store
AX 2012 R3 for Retail - Online Store, Brick-and-Mortar Stores, and Call Center


BASIC OVERVIEW

1. Setup pre-requisite: The existing Microsoft Dynamics AX email notification infrastructure has been leveraged for this feature.  For additional information on configuring the email functionality in AX, see the following TechNet article: Configure email functionality in Microsoft Dynamics AX  https://technet.microsoft.com/en-us/library/aa834374.aspx

2. Configure the how the email messages will look when sending to customers.  Go to: Organization administration >> Setup >> E-mail templates
You will notice that out of the box Microsoft has included default email templates as samples to get you started.  Please modify these or create new ones to meet your business requirements.

    

     Example e-mail:
    

3. Configure the E-mail templates to their related sales order actions.  Go to: Retail >> Setup >> Parameters >> Retail Email notification profile
You can create multiple email notification profiles but only one can be set as the default in the Retail Parameters.  When configuring the profile, you will have the option to select and activate several email notification types.  The Email notification types are hardcoded specific events AX.  Each will generate their unique email message by using the assigned email template (defined as the E-mail ID on this form).

Customers can be notified for the following activities:
     a. Order created: An email notification can be sent when a new order is created for a customer.
     b. Order confirmed: An email notification can be sent when an order is confirmed.
     c. Picking completed: An email notification can be sent when the order items are picked for packing at a store or a distribution location.
     d. Packing completed: An email notification can be sent when the packing is complete and order items are ready to be shipped.
     e. Order shipped: An email notification can be sent when the order is shipped, advising the customer of the delivery date and tracking information based on the shipping method selected.
     f. Payment failed: Email notification can be sent advising the customer regarding payment failure for the order.
     g. Customer created: Email notification can be sent for new customers.
     h. Password reset: Email notifications can be sent to advise customers when their account password is reset.

    

4. Set the default Email notification profile. Go to: Retail >> Setup >> Parameters >> Retail Parameters >> General >> Email notification profile
Select the email notification profile that will be used to automatically generate email messages to recipients based on users configured parameters.

    

5. To process the email notifications, go to: Retail >> Periodic >> Send email notifications. 
     a. It is recommended to set this up as with Batching processing to use the SMTP Server.  Set up the Recurrence to ensure timely emails are being sent.
     b. If you select to process this outside of batch, it will attempt to send emails from the local clients default email client. 

    

6. Once an order has been processed either Online, at the Store, or through Call Center along with any of the AX events of order created, confirmed, picked, packed, etc., the Send email notification batch processing will recognize the need to send the corresponding events email.  If you would like to modify or view how these events are recognized and tracked, view the following Class in the AOT:  RetailEventNotificationProcessor.

    

If you have any setup or configuration issues, please open a case with the support team.  Otherwise please share your general comments, ideas, or brief experiences below.

If you would like information on sending email receipts for POS transactions, click on the blog link below:
http://blogs.msdn.com/b/axsupport/archive/2015/03/06/sending-email-receipts-from-pos-transactions.aspx

Recently shared a blog post about Change fixed asset group this post will highlight the Reclassification function of the fixed asset, this used in case it is required to reclassify the asset from the accounting perspective and grouping as well. This function changing the asset group by canceling the old one and create a new fixed asset, and will  generate a financial entry.

The scenario here as the following we have an original fixed assets, and it is already acquired, then it will be reclassified to a new fixed asset ID, and this will close the original asset, reverse its acquisition entry, in the other hand will acquire the new asset. The below diagram illustrate the reclassification process between the original, and new asset.

In order to reclassify acquired fixed asset, go to  Fixed assets| Periodic| Reclassification.

In the dialog box identify the required information, the asset of which will be reclassified, and the new asset.

You’ll see the two assets the old and the new.

 The old is closed, by reversing the acquisition entry and the new is acquired.

The following screen shot represent the old asset

The following screen shot represent the new asset

The old asset acquisition transaction is reversed

The new asset is acquired

The reversal of old acquisition entry and the new acquisition entry are in the same voucher, the debit and credit side are representing the following;

Debit is representing the acquisition account of the new asset. Credit is representing the acquisition account of the old asset.

Versions: AX 2009/2012R2/2012R3 – not 2012RTM/FP

We introduced the possibility to enhance the Security for Microsoft Dynamics AX Server client communication.

By default we are using a Kerberos and NTLM mix. This stays unchanged if you don’t set any Registry Key.

For switching of the NTLM authentication in your environment we have now the possibility to switch to Kerberos only.

Here is how:

You need only to set on the server and client side the Registry key in the tree:

For the server: 　HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dynamics Server\"AX Version"\"instance for AX"\"configuration of the instance"

For the client: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Dynamics\"AX Version"\Configuration\"Name of Configuration"

Key: authn_service(string-value) with the Value 16

This is the minimum bar and has to be done for every AOS instance and client configuration.

For the client you also can do the change over the Config file by placing the key at the end of the file:

authn_service,text,16

These steps will trigger that the AOS is register a SPN for the instance during the start of the service.

Of cause only if the AOS service account is allowed to do this.

If not you have to register the SPN permanent manually.

If the AOS did register the SPN proper you should see in the Application event log an entry like:

Object Server 01: Authn Service: Kerberos

　SPN: 29D16D8E-32D1-433B-B77F-987C2408CEA4/contoso3209.Contoso.com:2712

On the client side you can check if the Client received his Kerberos ticket by using the tool Klist and the command "Klist tickets"

Outcome should look like:

Server: 29D16D8E-32D1-433B-B77F-987C2408CEA4/contoso3209.contoso.com:2712@contoso.COM

KerbTicket Encryption Type: test contoso WS(NT)

　　　　　 End Time: 3/31/2014 18:52:04

　　　　　 Renew Time: 4/1/2014 20:42:

Additional Keys possible:

authn_service(string-value)

- configurable on both client and server

- allowable values: 9, 16

　　　　　　　 9 = Negotiate,

　　　　　　　 16 = Kerberos

　　　　　　　 (default value is "Default" i.e. NTLM)

authn_regspn(string-key)

- configurable on server

- event log will show error if server failed to registered SPN

- allowable values: 0, 1

　　　　　　　 0 = do not register spn

　　　　　　　 1 = register spn (default value)

authn_fqdn(string value)

- configurable on client

- allowable values: 0, 1, domain suffix

　　　　　　　 0 = do append domain suffix

　　　　　　　 1 = append domain suffix (default value)

　　　　　　　 <string> = domain suffix (ex. mydomain.corp.com)

　　　　　　　 note: if there is no domain suffix supplied by the client config / ax load balance, the domain of the client machine is used.

authn_usehost(string value)

- configurable on client / server

- allowable values: 0, 1

　　　　　　　 0 = do not use host format (default)

　　　　　　　 1 = use host format

debugrpc(string-value)

- allowable values: 0, 1

　　　　　 　　0 = disables event log debug logging

　　　　　　　 1 = enables event log debugging

- configurable on server or client

- logs additional information regarding SPN registration, authentication mode, and SPN value.

Writer: Uwe Zimmermann <uwezim@microsoft.com>

AX 2012 RTM/R2/R3

We have in support received some queries for recommendations moving the AXModelStore to a database with different collation.

Conclusion: 

The AXModelStore file we create is specific to SQL_Latin collations. There should not be an issue (we are aware of)

when we are importing the AXModelStore file from one (Source environment) to another (Target environment) having different collations.

However, we would recommend to have same collations to ensure that we don't run into any issue.

In Microsoft Dynamics AX for Retail EPOS, there is not a lot of documentation on training mode.  Training mode can be used to test sales transactions and not record the transactions in Dynamics AX.  The cash drawer will not open and credit card, debit card, check and cash transactions will not be processed.

When POS is in training mode, the transactions that are created will have an Entry Status in the RetailTransactionTable with a value of 3 (Training) and the Transaction Status in the RetailTransactionSalesTrans will have a value of 3 (Training).  When running the P Job, the transactions will be moved to Headquarters, but these transactions will not be affected when creating, calculating and posting a statement

What you could do is create a POS Terminal in AX that is just a training terminal.  You could then not sync this terminal back to Headquarters if you do not want to see the Training transactions in Headquarters.

Note:  You will not be able to activate training mode for MPOS or the Online Stores.

Below are the settings to activate training mode in POS:

Navigate to Retail > Common > Retail channels > Select your store > Miscellaneous fast tab

Hide training mode should be unmarked.

When you create a sales transaction, I like to add the Messages section to the layout so I know it is in training, but this is not necessary. 

Retail > Setup > POS > Screen layouts

Click Designer button

In Screen layout designer, click Design mode drop down and select Main layout

In the Hidden Items tab, select Messages and drag to the layout.

Position the field as you would like

If you change the Store setting to not hide training mode, you must run the Channel configuration job to push this change to POS.

If you change the POS layout, you must run the Registers job to push the change to POS.

In POS, Activate training:

When logging into POS, select the arrow next to the X button (lower right) and select Activate training

You should see Training in the sign in window

We added the messages field to the layout, so you can see POS is in training mode.

When you tender the transaction, you should get a message that POS is in training mode

To Deactivate Training mode once you are in Training mode, go back to the sign on screen and select the X again and Deactivate Training.

Starting with the March release we've introduced a new feature in LCS for Crash and Hang analysis. Currently the feature is in the Beta phase, so it will need to be activated from the "Preview feature management" menu - "Public preview features" - "Crash and Hang Analysis".

After you activate the feature, it will appear as a tab in the System diagnostic tool.

To use this tool, collect a process dump file (.DMP), ZIP it and upload it onto the server using the steps below.

It will take between 30 minutes and two hours for the file to be processed on our servers. The result is an HTML report that contains details about the crash such as crash signature, AX kernel information, list of known issues, list of active sessions, X++ and native call stacks for all threads.

The search for known issues is done based on the names of the functions from the faulting call stack. For instance, if the call stack of the crashing thread contains the method 'Ax32Serv!SqlConnectBase::removeStmt', the report will look for hot-fixes that patch this method, such as KB 3017292, and provide a link to the Issue Search tool on LCS.

 Steps to Upload

1. From the tool's main page, press Add to create a new job

2. Provide a name and an optional description for the analysis job

3. Press Add files

4. Select .ZIP file containing one or more .DMP files and press Upload 

5. Press Analyze dumps

6. Confirm start of analysis

7. Wait until processing completes. This can take between half and hour and two hours depending on the complexity of the dump files.

8. After the job is marked as Completed, an HTML report is available. If you can't see it, refresh the web page.

 9. Open the report by pressing the icon in the View column

In this report you can see information about:

• AX kernel version
• Relevant hot-fixes
• Faulting call stack
• X++ and native call stacks for all threads

This blog posts assumes a working knowledge
of the Transportation management (TMS) module in Microsoft Dynamics AX 2012 R3

In Transportation management module of AX 2012 R3 there
exist freight engines. These engines are used to calculate costs for
freight loads. Some of the engines make use of LTL Freight class codes in their
calculation. In this blog you will learn how to associate an LTL code with an
NMFC code and associate an NMFC code to an item. The end result will be an
automatic association of an item to an LTL code.

Steps

1)     
In the Transportation management module create
your LTL class code.

a.  Transportation management | Setup | General LTL class

 
 
b. In the LTL class form click New

                                                              
i.     
LTL class = 92.5

                                                            
ii.     
Name = 92.5

                                                           
iii.     
Class = 92.5

                                                          
iv.     
Close the LTL class form

2)     
In the Transportation management module create
an NMFC code and associate the LTL class code to it

a.  Transportation management | Setup | General |
NMFC codes

b.  In the NMFC code form click new

                                                              
i.     
NMFC code = 92.5

                                                            
ii.     
Name = Electronics

                                                           
iii.     
LTL class = 92.5

                                                          
iv.     
BOL handling type = Unit

                                                            
v.     
Close the form

3)     
Finally the NMFC code must be associated to a
product. It is important to note that because NMFC code associations are
consistent that the relationship is setup in the “Product details” form and not
the “Released product details” form. The controls to assign an NMFC code to a
product in the “Released product details” form are disabled.

a.  Product information management | Common |
Products | Products

                                                              
i.     
Select any product and click Product | Maintain
| Edit on the panel

                                                            
ii.     
In the Product details from on the Warehouse
management fast tab set the NMFC code = 92.5

                                                           
iii.     
Save the form

                                                          
iv.     
Now anytime that item is rated the LTL code
should automatically populate.

We often work on cases where an item position is not kept together on one page even though the "KeepTogether" property is set to "True" on the Details Group. The reason is that the Details Group is not treated by the SSRS as a regular group used for grouping data. Hence, a possible solution to this issue is to add a parent group around the Details Group.

Here are the steps that helped to achieve it in the standard SalesInvoice report:

1. Open the SalesInvoiceReport project for editing in Visual Studio (detailed steps can be found here).

2. In the Model Editor, expand the Designs node, right click on the Report design and select Edit Using Designer…

3. In the Designer editor, click inside the first tablix in the report layout (table16) and toggle the grouping pane to Advanced mode view by right clicking the down arrow on the right side of the pane and selecting Advance mode.

4. In the grouping pane, right click on the details group tables16_Details_Group and select Add Group/Parent Group.

5. In the Tablix group dialog box, select [ItemId] for Group by and press OK.

This will add a grouping column in front of the tablix and the group Group1 will appear above the Details Group in the grouping pane.

6. Right click on top of the grouping column in the tablix and select Delete Columns.

7. In the Delete Columns dialog box, select Delete columns only and press OK.

8. In the grouping pane, set the properties for both static header rows as follows:

9. Right click on the created group Group1 and select Group Properties.

10. In the Group Properties form, click on Sorting and on the Sort by line in the Change sorting options pane, press Delete and OK.

This will allow to preserve the original sorting order of the order lines as they appear on the form.

11. Before saving and deploying the report, adjust the report width to its previous width as it was increased automatically when the grouping column was added to the tablix in step 5.

Set the width of the Rectangle InvoiceItemsRectangle and of the body to the value that does not exceed page width - left margin - right margin as otherwise each page might be split into two pages.

12. Save and deploy the report.

--author: Jolanta Malkowska

The goal of this post will be to walk through the necessary AIF setup required to utilize the Send button in the Account Payable Journal Voucher form. 

Clicking on the Send button without setup will result in an error message without much description on how to configure the necessary end point. 

Message: “No endPoints are configured for this action”

Step 1: Enable and Deploy Endpoint

1. In the AX client navigate to System Administration > Setup > Services and Application Integration Framework > Outbound Ports
2. Create a new Outbound Port and provide a Port Name, e.g. APPay
3. Set the Adapter type to File system adapter
4. Set the URI to the directory you wish to write the file out to, e.g. C:\APOutbound
5. Click on the Service Operations button in the Service Contract Customizations fast tab
6. Search through the Remaining Service Operations and find LegderVendorPaymentService.find
7. Select this operation and use the arrow buttons to move it to the Selected Service Operations side
   
8. Click Close
9. Click Activate to activate the service
   

Step 2: Configure End Point in Send Document Form

1. In the AX client navigate to Accounts Payable > Payments > Payment Journals
2. Select your Journal and click on Line to open the voucher form
3. Click the Send… button
4. In the Port Name drop down select the newly created outbound service, e.g. APPay
   
5. Click Ok to output file

Additional configuration: AIF outbound process will need to be configured and running to pick up and process this output.  For documentation on configuring AIF processing in batch see the additional document below.

Configuring batch jobs and tasks for AIF [AX 2012]

https://technet.microsoft.com/en-us/library/hh352328.aspx

What to select in Visual Studio under Tools > Options > Source Control as “Plug-in Selection”,

when using TFS as Dynamics AX 2012 Version Control System?

Recommendation:

When you select Microsoft Dynamics AX Version Control (This is what recommended to select),

you are selecting the Version Control that must be managed by AX.

You will still be using TFS, but it is managed by AX and not by Visual Studio.

If you select Visual Studio Team Foundation server, you are using TFS, but bypassing AX,

which we don’t recommend for AX objects in Visual Studio.

If you use the Visual Studio TFS (instead of the TFS through AX), you have then to manage

the files and their locations on the TFS server, which may not be equivalent to how AX expects them,

especially when dealing with Models.

AX organizes its source file by Model folder and element type folder to facilitate the synchronization,
building and deployment of Models. This is one of the main advantages of letting AX manages Source Control.