Docs :
https://drive.google.com/file/d/0Bz2gDlDZfIivejhTcWRTeExfSmc/edit?usp=sharing
https://drive.google.com/file/d/0Bz2gDlDZfIivdWNzUUZuOFZUNHc/edit?usp=sharing
===================================================================
http://learnax.blogspot.in/2012/01/dynamics-ax-2012-workflow-development.html -- Workflow
http://vimeo.com/26902748
http://www.youtube.com/watch?v=v13kASc5XKg
Main Change 2012 :
-> Whole presentaion layer out of Morphx is removed from AX and moved to VS. Adv : It gives control to over all .Net controls and 3rd party controls.
Architecture of EP :
1. Users who use EP
2. Browsers
3. Once log on to EP - MOSS 2007- MSoffice sharepoint Service 2007 .Windows Share point - 3.0 . diff webparts, outer box webparts, there is no limitation on Webparts used in EP .
User controls webpart - is a web part which allow to host any standard ASP.net User control.
Key steps as developer : Morphx - Business Logic and data modeling .
create dataset,table , create classes in Morphx, VS - Create User control, Go to share point and post User control in User control webpart.
User Control : Collection of UI Controls - like lookup, popup,Grid, form or any standard AX controls and third party control( silver light control )
Outerbox Credit Control - Ex demo - to show customer
Base of all these is the AX data source control - - .net Business connector - AXDatasource control - It allows u to access all meta data and Data in form of EPI . These EPI are consumed by AX data source control which provides access to data to all UI Control.
AX Datasource - We have to build our Databinding store on top of ASP.net datasource .
ie., As ASP.net have Databinding store , Data source - AXData source ctrl, DataBound- AXBoundField
Reports Webpart : Allows you to host any report built in Reporting Services.
Guiding Principle when came to EP architecture:
1. we shld have programing model which is similar to that of AX 2009 client. We dn't want steep curve for the developer in building EP apps. The articrafts built in AOT for AX EP, are very similar to accounting parts in client. ex; webmenu similar to menu.
2.we have AOT -Data modeling VS - VS Ctrl, Share point - To create Web pages We want to unify all artificants to single AOT store. Help to have single security model that can be to client as well as EP.Since everything sit in AOT , we can apply same security model as Client articrafts.
Advantages over X++ Based framework over ASP.net Based Framework ie., Web UI framework:
1. If you can built a functionality on Standard ASP.net web application you can develop in EP. There is no stoping of using any controls there.
2. Built of AJAX in to the framework itself. if you want use webpart to host our user control , we dn't want to worry how to integrate.. We can use AJAX on EP.
3. Extend
4. Managed Code developement - We need to use X++ for UI rendering but now we are using ASP.Net for UI rendering.
Advantages over traditional ASP.Net Solution :
=============================================
1. Data binding everything is built in framework itself .. so no need to worry in EP
2. Field group is specific to AX not ASP.Net . We can access field group in EP even. At design time it is single field in markup and at run time it would easily explore to multiple fields .
Nodes which are specific to EP :
==============================
1. Dataset node
2. Web
i) Web Menus
ii) Web menu Itms
iii) Files - Web user Controls are saved.
iv) Page Definition node - where all share point pages are saved.
v) Web content >> managed - have all user controls.
Difference b/w datasets and Form data sources is Design is missing in Datasets.
First Demo : Customer Listing on to EP with out writing any single code :
1. Create Data Set - EPDevWebinar(name) - Add Data source - CustTable .
2. Go to EP ie., VS File - NEw Web site > >DYnamics AX Web Project >> Name - EPDEVWebinar.
3. RC on EPDEVWebinar >> Add New Item >> Dynamics AX User Control>>EPDEVwebinarUC1(name) >> RC on it >> Add to AOT.
Imp: We not only add templates but integrated AX with VS.
4. Check AOT>> WebFiles >> and Webcontent >> Managed >> we find the user control .
5. Go to design mode in VS for Control .
6. Bring AX Data source on to the design and Properties ( EPDevWebinar - data set we created in AOT).(Click refresh Schema if you dn't find the Dataset created.
7. Drop Grid and set AXDatasource1 which we added before in design.
8. Edit columns >> pick fields needed . Save it.
9. Go to EP >> click the URL of EPSite . ( create new page how it renders in to EP)
10. Site Actions >> Create Page >> New Part Page >> To create new page , create New Web Part Page.
11. Wepage >> WebPartpage >> name EPDEVWebinar Page1, Document Library - Enterprise Portal.
12. under Dynamics Infolog Webpart - Add new web part , select Dynamics user control webpart >> Click modify select the user control developed in VS.
(ONce you saved User control on VS - Not only saved to AOT, it deployed to EP )
Demo : 2 - Custom Filter :
==========================
Add Employee ID field in Grid.
We neeed to add 2 methods in Dynamics AX.
Go to Data set EPWebinar we created, add two methods.
1. Void AllCustomers()
{
querybuilddatasource qdbs;
QueryBuildRange qbr;
;
qdbs = CustTable_q.dataSourceName(CustTable_ds.name());
qdbs.clearRange(fieldnum(CustTable,EmpId);
CustTable_ds.executeQuery();
}
2. Void MyCustomers()
{
querybuilddatasource qdbs;
QueryBuildRange qbr;
;
qdbs = CustTable_q.dataSourceName(CustTable_ds.name());
qdbs.clearRange(fieldnum(CustTable,EmpId);
qbr - qbds.addRange(fieldnum(CustTable, EmpId));
qbr.value(SysQueryRangeUtil::CurrentEmployeeId(); // Employee for the logged in User .
qbr.status(RangeStatus::Open);
CustTable_ds.executeQuery();
}
Go back to VS >> refresh Schema in Grid . Go to Source and Add Below code.
Go to design mode - Properties of Click ,Items (Click Add - All , My) AutoPostBack - True. Go to Event - SelectIndex Changed.
We need to Administration >> refresh AOD in EP environment.
Demo : 3 : how you can use standard asp.net template :
====================================================
Add one more field Terms of payment( paymentTerm Id) in grid.
we want to display images or icons tht represent the values for different values of Payment ID. - M15, M30 ...
1. Select the PaymentTermId - click convert to template field ...
When you see the code regarding the control, we have two codes - EditItemtemplate - When grid is shown in edit mode -Dynamic change, ItemTemplate - When grid is shown in view mode -static
2. Change Item Template Code with Image and Label.
Having two controls, to control visibility based on the value.
Demo 4 : Date Control , how it is shown in EP
============================================
1. Change the mode of the grid , AllowEdit = "true"
2. Add field Appeciation date. - A date field is brought in grid.
If we want to have Date field, such that we can have 3 drop downs- Day of month,month, Year - >
Demo : 5 Web Associations - how to connect two webparts in a page and how they can to one another
1. Add new user control - EPDevWebinarUC2>> Add to AOT.
Add two methods under data soruce:
1. dispaly NumberOfRecords TotalOrders(CustTable _custTable)
{
Salestable salesTable;
;
select count(recId) from salesTable where salesTable.InvoiceAccount == _custTable.AccountNum &&
(salesTable.salesStatus == SalesStatus::Backorder ||
salesTable.salesStatus == SalesStatus::Deliverd ||
salesTable.SalesStatus == SalesStatus::Invoiced);
return salesTable.Recid;
}
2. dispaly NumberOfRecords openSalesOrders(CustTable _custTable)
{
Salestable salesTable;
;
select count(recId) from salesTable where salesTable.InvoiceAccount == _custTable.AccountNum &&
(salesTable.salesStatus == SalesStatus::Backorder ||
salesTable.salesStatus == SalesStatus::Deliverd);
return salesTable.Recid;
}
2. Add Data source to user control - EPDevWebinar - Data SetName - EPDevWebinar.Click refresh schema - to get newly added methods.
Add AX form - Data SourceID - AxDataSource1, DataMember - CustTable_Current, DatKeyname - AccountNum_name Name - a, AXGrid.
Add group to Form - add Fields - Open sales orders, Total sales orders.
Copy the fields ( display methods ) if code is not added in source code.
Add User control to the new web part >> modify the property ,
Webpart Role -
none - not going to participate in any connections, provider - provide the context, consumer - consume the context.
Change the other user control to Provider.
Modify Shared webpart >>
Connections >> send AXControlList to >> Dynamics UserControlWebpart[2].
Demo 6: Chart :
=================
Add Chart Control to Design .
Set the data source. - to datasource already created .
Click Series.
Series - add two fields - total orders and Open orders.
click >>
Char area - 3d property to - true.
If you want to add legend... we can do it.
Demo : 7 To create Insert Edit form :
=======================================
Create a user control..
add >> data source , Form. To form Add Multi section, add ax sections. to each section add group.
They allow you to have collapsable control to the form.
Bound field - to add fields.
Bound Field Groups - to add Field group.
To have view only, edit or insert mode to form ,
below is the code.
https://drive.google.com/file/d/0Bz2gDlDZfIivejhTcWRTeExfSmc/edit?usp=sharing
https://drive.google.com/file/d/0Bz2gDlDZfIivdWNzUUZuOFZUNHc/edit?usp=sharing
===================================================================
http://learnax.blogspot.in/2012/01/dynamics-ax-2012-workflow-development.html -- Workflow
http://vimeo.com/26902748
http://www.youtube.com/watch?v=v13kASc5XKg
Main Change 2012 :
-> Whole presentaion layer out of Morphx is removed from AX and moved to VS. Adv : It gives control to over all .Net controls and 3rd party controls.
Architecture of EP :
1. Users who use EP
2. Browsers
3. Once log on to EP - MOSS 2007- MSoffice sharepoint Service 2007 .Windows Share point - 3.0 . diff webparts, outer box webparts, there is no limitation on Webparts used in EP .
User controls webpart - is a web part which allow to host any standard ASP.net User control.
Key steps as developer : Morphx - Business Logic and data modeling .
create dataset,table , create classes in Morphx, VS - Create User control, Go to share point and post User control in User control webpart.
User Control : Collection of UI Controls - like lookup, popup,Grid, form or any standard AX controls and third party control( silver light control )
Outerbox Credit Control - Ex demo - to show customer
Base of all these is the AX data source control - - .net Business connector - AXDatasource control - It allows u to access all meta data and Data in form of EPI . These EPI are consumed by AX data source control which provides access to data to all UI Control.
AX Datasource - We have to build our Databinding store on top of ASP.net datasource .
ie., As ASP.net have Databinding store , Data source - AXData source ctrl, DataBound- AXBoundField
Reports Webpart : Allows you to host any report built in Reporting Services.
Guiding Principle when came to EP architecture:
1. we shld have programing model which is similar to that of AX 2009 client. We dn't want steep curve for the developer in building EP apps. The articrafts built in AOT for AX EP, are very similar to accounting parts in client. ex; webmenu similar to menu.
2.we have AOT -Data modeling VS - VS Ctrl, Share point - To create Web pages We want to unify all artificants to single AOT store. Help to have single security model that can be to client as well as EP.Since everything sit in AOT , we can apply same security model as Client articrafts.
Advantages over X++ Based framework over ASP.net Based Framework ie., Web UI framework:
1. If you can built a functionality on Standard ASP.net web application you can develop in EP. There is no stoping of using any controls there.
2. Built of AJAX in to the framework itself. if you want use webpart to host our user control , we dn't want to worry how to integrate.. We can use AJAX on EP.
3. Extend
4. Managed Code developement - We need to use X++ for UI rendering but now we are using ASP.Net for UI rendering.
Advantages over traditional ASP.Net Solution :
=============================================
1. Data binding everything is built in framework itself .. so no need to worry in EP
2. Field group is specific to AX not ASP.Net . We can access field group in EP even. At design time it is single field in markup and at run time it would easily explore to multiple fields .
Nodes which are specific to EP :
==============================
1. Dataset node
2. Web
i) Web Menus
ii) Web menu Itms
iii) Files - Web user Controls are saved.
iv) Page Definition node - where all share point pages are saved.
v) Web content >> managed - have all user controls.
Difference b/w datasets and Form data sources is Design is missing in Datasets.
First Demo : Customer Listing on to EP with out writing any single code :
1. Create Data Set - EPDevWebinar(name) - Add Data source - CustTable .
2. Go to EP ie., VS File - NEw Web site > >DYnamics AX Web Project >> Name - EPDEVWebinar.
3. RC on EPDEVWebinar >> Add New Item >> Dynamics AX User Control>>EPDEVwebinarUC1(name) >> RC on it >> Add to AOT.
Imp: We not only add templates but integrated AX with VS.
4. Check AOT>> WebFiles >> and Webcontent >> Managed >> we find the user control .
5. Go to design mode in VS for Control .
6. Bring AX Data source on to the design and Properties ( EPDevWebinar - data set we created in AOT).(Click refresh Schema if you dn't find the Dataset created.
7. Drop Grid and set AXDatasource1 which we added before in design.
8. Edit columns >> pick fields needed . Save it.
9. Go to EP >> click the URL of EPSite . ( create new page how it renders in to EP)
10. Site Actions >> Create Page >> New Part Page >> To create new page , create New Web Part Page.
11. Wepage >> WebPartpage >> name EPDEVWebinar Page1, Document Library - Enterprise Portal.
12. under Dynamics Infolog Webpart - Add new web part , select Dynamics user control webpart >> Click modify select the user control developed in VS.
(ONce you saved User control on VS - Not only saved to AOT, it deployed to EP )
Demo : 2 - Custom Filter :
==========================
Add Employee ID field in Grid.
We neeed to add 2 methods in Dynamics AX.
Go to Data set EPWebinar we created, add two methods.
1. Void AllCustomers()
{
querybuilddatasource qdbs;
QueryBuildRange qbr;
;
qdbs = CustTable_q.dataSourceName(CustTable_ds.name());
qdbs.clearRange(fieldnum(CustTable,EmpId);
CustTable_ds.executeQuery();
}
2. Void MyCustomers()
{
querybuilddatasource qdbs;
QueryBuildRange qbr;
;
qdbs = CustTable_q.dataSourceName(CustTable_ds.name());
qdbs.clearRange(fieldnum(CustTable,EmpId);
qbr - qbds.addRange(fieldnum(CustTable, EmpId));
qbr.value(SysQueryRangeUtil::CurrentEmployeeId(); // Employee for the logged in User .
qbr.status(RangeStatus::Open);
CustTable_ds.executeQuery();
}
Go back to VS >> refresh Schema in Grid . Go to Source and Add Below code.
Go to design mode - Properties of Click ,Items (Click Add - All , My) AutoPostBack - True. Go to Event - SelectIndex Changed.
We need to Administration >> refresh AOD in EP environment.
Demo : 3 : how you can use standard asp.net template :
====================================================
Add one more field Terms of payment( paymentTerm Id) in grid.
we want to display images or icons tht represent the values for different values of Payment ID. - M15, M30 ...
1. Select the PaymentTermId - click convert to template field ...
When you see the code regarding the control, we have two codes - EditItemtemplate - When grid is shown in edit mode -Dynamic change, ItemTemplate - When grid is shown in view mode -static
2. Change Item Template Code with Image and Label.
Having two controls, to control visibility based on the value.
Demo 4 : Date Control , how it is shown in EP
============================================
1. Change the mode of the grid , AllowEdit = "true"
2. Add field Appeciation date. - A date field is brought in grid.
If we want to have Date field, such that we can have 3 drop downs- Day of month,month, Year - >
Demo : 5 Web Associations - how to connect two webparts in a page and how they can to one another
1. Add new user control - EPDevWebinarUC2>> Add to AOT.
Add two methods under data soruce:
1. dispaly NumberOfRecords TotalOrders(CustTable _custTable)
{
Salestable salesTable;
;
select count(recId) from salesTable where salesTable.InvoiceAccount == _custTable.AccountNum &&
(salesTable.salesStatus == SalesStatus::Backorder ||
salesTable.salesStatus == SalesStatus::Deliverd ||
salesTable.SalesStatus == SalesStatus::Invoiced);
return salesTable.Recid;
}
2. dispaly NumberOfRecords openSalesOrders(CustTable _custTable)
{
Salestable salesTable;
;
select count(recId) from salesTable where salesTable.InvoiceAccount == _custTable.AccountNum &&
(salesTable.salesStatus == SalesStatus::Backorder ||
salesTable.salesStatus == SalesStatus::Deliverd);
return salesTable.Recid;
}
2. Add Data source to user control - EPDevWebinar - Data SetName - EPDevWebinar.Click refresh schema - to get newly added methods.
Add AX form - Data SourceID - AxDataSource1, DataMember - CustTable_Current, DatKeyname - AccountNum_name Name - a, AXGrid.
Add group to Form - add Fields - Open sales orders, Total sales orders.
Copy the fields ( display methods ) if code is not added in source code.
Add User control to the new web part >> modify the property ,
Webpart Role -
none - not going to participate in any connections, provider - provide the context, consumer - consume the context.
Change the other user control to Provider.
Modify Shared webpart >>
Connections >> send AXControlList to >> Dynamics UserControlWebpart[2].
Demo 6: Chart :
=================
Add Chart Control to Design .
Set the data source. - to datasource already created .
Click Series.
Series - add two fields - total orders and Open orders.
click >>
Char area - 3d property to - true.
If you want to add legend... we can do it.
Demo : 7 To create Insert Edit form :
=======================================
Create a user control..
add >> data source , Form. To form Add Multi section, add ax sections. to each section add group.
They allow you to have collapsable control to the form.
Bound field - to add fields.
Bound Field Groups - to add Field group.
To have view only, edit or insert mode to form ,
below is the code.
No comments:
Post a Comment