Ax Techie Blog

Wednesday, 24 August 2016

Role based Security in AX

· To setup security roles to a user need to follow following hierarchy

· Create Security role

Go to System administration > setup > security > security roles

Give security role name by clicking new button

· Create Duties, privileges and permission

Go to System administration > setup > security > security privileges

Click new to create a new process cycle, again click new to create duty, again click new to create new privilege

By keeping the cursor on newly created privilege, add permission and give access level

· Assign duties to the role

Go to System administration > setup > security > security roles

Select your security role and click on Add in role content then select the duty and privilege from your process cycle

Assigning user to roles

Go to System administration > setup > security > Assign users to roles

Select your role and click on manually assign/exclude user from users assigned to role and select the users

Now Logon to Microsoft dynamics AX with the assigned user login credentials and check the permission level you applied is working or not

Note: 1. for system administrator role no privilege takes effect as he has full control

Thursday, 30 June 2016

X++ Program to print 143 as 100+40+3

static void Job10(Args _args)
{
int r,n,i,j;
real mul=0.1,q;
str k;
;
n = 143;
q = n;
for(i=1;q>=1;i++)
{
mul = mul * 10;
r = (q mod 10)*mul;
q=q/10;
if(k)
k = int2str(r)+"+"+k;
else
k=int2str(r);
}

info(k);

Saturday, 14 May 2016

Update the records in table with validtimestate

ttsBegin;

HcmEmploymentEmployee.selectForUpdate(true);
HcmEmploymentEmployee.validTimeStateUpdateMode(ValidTimeStateUpdate::Correction);
HcmEmploymentEmployee.ProbationEndDate = DateTimeUtil::addDays
(employmentStartDate,HcmEmploymentEmployee.ProbationDays-1);
hcmEmploymentEmployee.update();

ttsCommit;

Wednesday, 16 March 2016

How to debug SSRS report RDP model in AX 2012

1. Verify whether you checked Enable break points, enable global breakpoints on server

2. Simply keep breakpoint; in your code

3. If that is not worked, then

a. In class declaration extend SrsReportDataProviderPreProcess instead of SRSReportDataProviderBase

b. Make changes of Temperory table properties as below
i. Table type --> Regular
ii. CreatedTransactionId --> Yes
4. Add below line in process method of DP class
Temptablename.setConnection(this.parmUserConnection());

Happy Daxing.....

Lookup() and jumpref() methods in AX 2012

1. Lookup method we can write at table level, form Data source level and Form control level.
Now writing at Data source level(Form: Organization hierarchy, Table: Organization hierarchy)

public void lookup(FormControl _formControl, str _filterStr)
{
SysTableLookup sysTableLookup = SysTableLookup::newParameters(tableNum(DivisionTable), _formControl);
Query query = new Query();
QueryBuildDataSource qbds,qbds1;

sysTableLookup.parmQuery(query);
sysTableLookup.addLookupField(fieldNum(DivisionTable, DivisionCode));
sysTableLookup.addLookupField(fieldNum(DivisionTable, DivisionName));
qbds = Query.addDataSource(tableNum(DivisionTable));
qbds1 = qbds.addDataSource(tableNum(DivisionCompanyLine));
qbds1.relations(true);
qbds1.addRange(fieldNum(DivisionCompanyLine, DataArea)).value(OrganizationHierarchy.Company);

sysTableLookup.parmQuery(query);
sysTableLookup.performFormLookup();
}

2. Writing jumpref() at Form DS level

public void jumpRef()
{
Args args;
MenuFunction menuFunction;
;
args = new Args();
menuFunction = new MenuFunction(menuitemDisplayStr(MenuItemName), MenuItemType::Display);
args = new Args(menuFunction.object());
args.caller(element);
menuFunction.run(args);
}

Friday, 5 February 2016

Pack() and unpack() methods in Dynamics AX

Pack and unpack is Dynamics language for serialization -- putting object-specific data in a writeable format and later reading it back to create an object in the exact same state.
Most of the interactive objects in Dynamics will automatically check for saved user data when invoked and instantiate accordingly. Perhaps you remember running a report and the next time you opened the report your previous query and parameter values were already there. This happens because of pack and unpack.
The majority of what makes pack and unpack confusing is macros, so let's do a simple example not using macros at all. Let's say we have a class that has two date values I need to persist between runs: startDate and endDate.
So when pack() gets called, I need to store both variables. (If you don't understand the way containers work, look them up on MSDN first, otherwise this won't make sense).
container pack()
{ return [startDate, endDate];
}
The framework will take whatever pack returns and store it in user data. So when the object is instantiated, unpack() gets called in order to reinitialize the values.
boolean unpack(container _packedValues)
{
[startDate, endDate] = _packedValues;
return true;
}
Follow what's happening here? We expect _packedValues to contain startDate and endDate in that order, so we assign those values to our class variables.
Now let's imagine we want to add another class variable that needs to be stored: isPosted
To do this, we'll have to modify our pack to return
[startDate, endDate, isPosted]
and our unpack to assign all three:
[startDate, endDate, isPosted] = _packedValues;
Hm, but what about values that were stored before our modification? That container assignment won't work because _packedValues will only contain 2 values (startDate and endDate). So let's make the first value in our packed data identify the version of the packed data so we can handle old values without crashing.
container pack()
{ return [1, startDate, endDate, isPosted];}
boolean unpack(container _packedValues)
{
boolean ret = true;
int version;
;
if (conpeek(_packedValues) == 1)
{
[version, startDate, endDate, isPosted] = _packedValues;
} else
{
ret = false;
}
return ret;}
Ok, so now if I need to add more variables, I need to change the version number in both pack and unpack, but now old data will make unpack() return false, which will initialize the parameter defaults.
So now let's add some macros so we only have to change one spot when we change what we want to pack. In our classDeclaration, we'll create 2 macros: one for the version of the data, and one for the values we wish to store.
classDeclaration()
{
#define.CurrentVersion(1)

#localMacro.CurrentList
startDate, endDate,
isPosted #endMacro }
If you're unfamiliar with macros, what they do is fill in exactly what the macro says at compile time. So whenever you write #CurrentVersion, the compiler fills in '1'. Whenever you write #CurrentList, the compiler fills in 'startDate, endDate, isPosted'. So now we can change our pack() and unpack() to look like this:
container pack()
{
return [#CurrentVersion, #CurrentList];
}
boolean unpack(container _packedValues)
{
int version; boolean ret = true;
;
if (conpeek(_packedValues) == #CurrentVersion)
{ [version, #CurrentList] = _packedValues;
}
else
{ ret = false; }
return ret;
}

Note:Copied from https://community.dynamics.com/ax/f/33/p/67248/122709

Tuesday, 5 January 2016

Installation of Hyper-v of AX7

Prerequisite to install AX7 Hyper-V
1.Drive size needed: 150GB
2.RAM: 12GB(16GB recommended
3.OS: windows 8/8.1/10(PRO) or windows server 2012/2012R2
4.Office365 account(atleast trail)

Step 1: Run application, that extracts remaining zips, constitute to 113GB