Hats off to Kurt once again, for this walkthrough on understanding mPOS reports:
https://kurthatlevik.com/2015/08/12/dax-2012-r3-retail-channel-pos-reports/
#noteToSelf
AXforRetail
Findings about AX for Retail
Tuesday, May 22, 2018
Understanding POS reports
Thursday, April 6, 2017
Editing license configuration requires *Maintenance Mode* - use Deployment.Setup tool
Today I tried to change license keys in Dynamics 365 for Operations to enable Commerce essentials license key. What was unexpected comparing to previous AX versions is that i could not do it.
The warning says:
This form is read-only unless the system is in the maintenance mode. Maintenance mode can be enabled in this environment by running maintenance job from LCS, or using Deployment.Setup tool locally
Luckily there is a long guide on AX wiki. To spare you some time here is all you need to know:
1. Navigate to your AOS folder (e.g. C:\AOSService\PackagesLocalDirectory\Bin
2. Press Shift on keyboard, hold it, right-click in Explorer
3. Paste this and change parameters with your variables:
Microsoft.Dynamics.AX.Deployment.Setup.exe -setupmode maintenancemode --metadatadir C:\AOSService\PackagesLocalDirectory --bindir C:\AOSService\PackagesLocalDirectory --sqlserver "." --sqldatabase "AxDB" --isinmaintenancemode true --sqluser Godzilla --sqlpwd 1
pay particular attention to Metadatadir, bindir, sqluser, sqlpwd parameters
4. Paste into the command line window
5. This is what you should get:
6. Type iisreset -noforce and press enter
7. Log back into Dynamics 365 for Operations
Now you'll be able to edit the license keys.
Once you do,
Remember to turn off the maintenance mode:
Microsoft.Dynamics.AX.Deployment.Setup.exe -setupmode maintenancemode --metadatadir C:\AOSService\PackagesLocalDirectory --bindir C:\AOSService\PackagesLocalDirectory --sqlserver "." --sqldatabase "AxDB" --sqluser Godzilla --sqlpwd 1 --isinmaintenancemode false
The warning says:
This form is read-only unless the system is in the maintenance mode. Maintenance mode can be enabled in this environment by running maintenance job from LCS, or using Deployment.Setup tool locally
Luckily there is a long guide on AX wiki. To spare you some time here is all you need to know:
1. Navigate to your AOS folder (e.g. C:\AOSService\PackagesLocalDirectory\Bin
2. Press Shift on keyboard, hold it, right-click in Explorer
3. Paste this and change parameters with your variables:
Microsoft.Dynamics.AX.Deployment.Setup.exe -setupmode maintenancemode --metadatadir C:\AOSService\PackagesLocalDirectory --bindir C:\AOSService\PackagesLocalDirectory --sqlserver "." --sqldatabase "AxDB" --isinmaintenancemode true --sqluser Godzilla --sqlpwd 1
pay particular attention to Metadatadir, bindir, sqluser, sqlpwd parameters
4. Paste into the command line window
5. This is what you should get:
6. Type iisreset -noforce and press enter
7. Log back into Dynamics 365 for Operations
Now you'll be able to edit the license keys.
Once you do,
Remember to turn off the maintenance mode:
Microsoft.Dynamics.AX.Deployment.Setup.exe -setupmode maintenancemode --metadatadir C:\AOSService\PackagesLocalDirectory --bindir C:\AOSService\PackagesLocalDirectory --sqlserver "." --sqldatabase "AxDB" --sqluser Godzilla --sqlpwd 1 --isinmaintenancemode false
Sunday, March 25, 2012
Retail 2012 virtual launch event
After AX convergence, there was a retail event.
To get inspired & motivated watch these exciting videos and demos:
- Watch the on-demand global Virtual Launch Event to see how leading retailers are using this solution to support rapid growth, and learn about the other powerful capabilities that are new to Microsoft Dynamics AX 2012, or
- Download the Gartner ERP strategy whitepaper. (this link did not work, try at your own risk).
You can follow @MSFTDynamicsERP on Twitter to learn about new exciting marketing materials.
Monday, February 6, 2012
OPOS Problems?
A step that is often overlooked after an OPOS driver install is the installation of common control objects from Monroe Consulting Services. They can be found here.
I faced the same troubleshooting problem when setting up HP rp5700 with Dynamics AX for Retail 2009.
I faced the same troubleshooting problem when setting up HP rp5700 with Dynamics AX for Retail 2009.
Saturday, January 21, 2012
Stack trace: The company XX does not exist. (S)\Classes\DirParty\updateAddressFromDirParty - line 149
This is a case worthy of Agatha Christie.
Starting conditions:
Error infolog appeared when saving an address for a vendor by a user, who has access to only a subset of virtual company's company set.
In other words: We have a virtual company that shares DirParty and Vendor tables. Let's say the companies in the virtual company are: 01,02,03,04,05. The user has permissions to access only 01 and 02.
The user creates a Vendor record. When adding the address, the error appears.
On a closer look, the DirParty class, method UpdateAddressFromDirParty has an interesting function: for a public address create address records in all the real companies which are the part of the virtual company. In our case 01,02,03,04,05.
So the conflict arises: The user only has permissions for 01 and 02, while the program wants to update more.
The solution is to introduce some sort of validation of whether the user has permission to the company, which AX is trying to update:
if(Sysdataarea::checkAccessible(dataAreaId)==false)
{
infolog.closeInfolog(100);
continue
}
That is a crude way to verify whether the user has access to the company Dynamics AX wants to update an address in.
Place this code right after the following line:
dataAreaId = conpeek(addressDataAreaList,i);
Of course, test it out before applying to a production environment.
Starting conditions:
Error infolog appeared when saving an address for a vendor by a user, who has access to only a subset of virtual company's company set.
In other words: We have a virtual company that shares DirParty and Vendor tables. Let's say the companies in the virtual company are: 01,02,03,04,05. The user has permissions to access only 01 and 02.
The user creates a Vendor record. When adding the address, the error appears.
On a closer look, the DirParty class, method UpdateAddressFromDirParty has an interesting function: for a public address create address records in all the real companies which are the part of the virtual company. In our case 01,02,03,04,05.
So the conflict arises: The user only has permissions for 01 and 02, while the program wants to update more.
The solution is to introduce some sort of validation of whether the user has permission to the company, which AX is trying to update:
if(Sysdataarea::checkAccessible(dataAreaId)==false)
{
infolog.closeInfolog(100);
continue
}
That is a crude way to verify whether the user has access to the company Dynamics AX wants to update an address in.
Place this code right after the following line:
dataAreaId = conpeek(addressDataAreaList,i);
Of course, test it out before applying to a production environment.
Tuesday, September 20, 2011
AX 2009 not importing the records into a virtual table
Not an AX4Retail post per se, but rather a generic finding.
Just had a situation where i've shared address tables to a virtual company. Did the re-import and the data did not appear in the target companies. The import also did import the data into the single company, not to the virtual company.
This was a strangely manefesting issue, given the fact that it was RU6 AX2009.
However a simple AOS restart fixed the whole situation. Now the address data.
Cause is unknown.
Just had a situation where i've shared address tables to a virtual company. Did the re-import and the data did not appear in the target companies. The import also did import the data into the single company, not to the virtual company.
This was a strangely manefesting issue, given the fact that it was RU6 AX2009.
However a simple AOS restart fixed the whole situation. Now the address data.
Cause is unknown.
Wednesday, August 31, 2011
Training for Dynamics AX for Retail in October 2011
Allright, finally we've got the link. You can register for the upcoming training here. It will be taking place in Atlanta, GA from the 3rd till 6th of October. Starts monday morning at 8 AM sharp!
As usual, two days of functionality-oriented stuff and two days of more technical stuff, mixed with more functionality. No programming assignments.
UPDATE: it is actually cancelled. I'll post here when/where is the next one i'm conducting..
As usual, two days of functionality-oriented stuff and two days of more technical stuff, mixed with more functionality. No programming assignments.
UPDATE: it is actually cancelled. I'll post here when/where is the next one i'm conducting..
Subscribe to:
Posts (Atom)