Apply Style

DEV and TEST

        On Dev

1.       Each team must use separate code prefix, label file and model:

a. All objects (except label file) must belong to model.

b. If development is going on DEV server - CUS layer must be used and

c. All changes must be checked in to MorphX VSS.

d. For development on other environments, please, use VAR layer.

To Test

                a. Delivery into TEST will be done by models.

                b. Delivery will be done during maintenance windows, so plan your work accordingly.

                c. Direct changes in TEST CUS layer are prohibited. If you need to apply quick fix/change you can do it in USR layer and move it to DEV. USR layer on TEST will be deleted on next deployment.

                d. If you are ready to move code to TEST:

- check that all objects are included in your model;

- check that code in model compiles without errors;

- notify my team. If you are ready with some piece, but you need to continue – please, export your model and label file in separate folder – and notify my team (same for external development).

Edit a page 

HTTP:\\MYSHAREPOINT?ToolPaneView=2&pagemode=edit

Args

static void OpenFormFunction()
{ 
Object formRun;
Args args = new Args();
;
args.name(formstr(CustTable));
args.record(CustTable::find('ABC'));

formRun = ClassFactory.formRunClass(args);
formRun.init();

formRun.yourmethodgoeshere(); /* !!

formRun.run();
formRun.wait();
}

AXModel

What is the difference between MenuItem types - Display, Action and Output
output normally run reports
action normally run classes
display normally run forms


PS C:\>Export-AXModel -model Packaging -file c:\models\Packaging.axmodel

This example installs the MyModel file into the same layer that it was exported from.
Any conflicts will be pushed to the related update layer.
PS C:\>Install-AXModel -File MyModel.axmodel -Conflict Push

http://technet.microsoft.com/EN-US/library/hh352314.aspx

DAX Cue

Create a table, then a query, next create a menuitem. The menu item will use the Query, if not a form involved, in the objectType, it's Query, Object: [QueryName]; if it has form, it's Form and FormName.
Lastly, create a cue, put the label name and MenuItemName.

When all's done, Cue can be added from the Form and EP.

To Create the Menu Item

1. In the AOT, expand Menu Items, right-click Display, and then click New Menu Item.
2. Click the new menu item. In the property sheet, click Name and specify a name that uniquely identifies the menu item.
3. Click Label and select the label for the menu item. The menu item label appears in the FactBox when the Label property of the cue is empty.
4. Click Query and then click the name of the query that you want to use to retrieve the data records.
5. Click ObjectType and select Form.
6. Click Object and then click the name of the form that you use to show the records from the query. If you do not want to open a form from the cue, you can leave the property empty.
7. If the cue appears in Enterprise Portal, click WebMenuItemName and select a WebMenuItem. Use a WebMenuItem that opens a list page that can display the set of records that the cue retrieved.
8. Right-click the menu item and then click Save.

To Create the Cue

1. In the AOT, expand Parts, right-click Cues, and then click New Cue. A cue is added to the list of Cues in the AOT.
2. Click the new cue. In the property sheet, click Name and specify a name that uniquely identifies the cue.
3. Click Label and select the label you want to appear in a FactBox. This step is optional. If the label is not specified, the cue uses the label from the menu item.
4. Click MenuItemName and select the menu item that you created for the cue. This menu item specifies the query you want to use, as well as the form (for the Microsoft Dynamics AX client) or list page (for EP) that will be opened when the cue is clicked.
5. Right-click the cue and then click Save.

Remove Duplicates

--select * from LOGISTICSADDRESSZIPCODE where ZIPCODE = '92620'

create table #TempRECID (myRecID bigint)

insert into #TempRECID (myRecID)
select A.RECID
from LOGISTICSADDRESSZIPCODE A
inner join LOGISTICSADDRESSZIPCODE B
on A.ZIPCODE = B.ZIPCODE
and A.COUNTY<>B.COUNTY
and B.COUNTY <> ''
--and B.ZIPCODE = '92620'

--select * from #TempRECID

delete AA from LOGISTICSADDRESSZIPCODE AA
inner join #TempRECID B on AA.RECID = B.myRecID
--where RECID = '5637148309'

drop table #TempRECID

--select * from LOGISTICSADDRESSZIPCODE where RECID =  '5637148309'

===========================================================
update dbo.LOGISTICSADDRESSZIPCODE
set ZIPCODE = '0' + ZIPCODE
where len(zipcode) = 4

Master Page and Logo

In dynamics ax 2012, you can change the logo from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ep\images\ location and change the name you your logo file to DynamicsLogo64x64.png

Dynamics AX 2009 Enterprise Portal was designed with templates compatible with SharePoint 2007, and they are in this compatible mode in SharePoint 2010. Hence not all features are compatible for example with SharePoint Designer. Hence you are unable to edit the master page using this tool. Even if you could edit the master page using the SharePoint Designer, every time you update Enterprise Portal, say using AXUPDATEPORTAL.EXE, it would override the default master page with the copy stored in the AOT.
So therefore to edit the master page do the following:
1. Go to: AOT\Web\Web Files\StaticsFiles\defaultax
2. Export defaultax object
3. Make a backup copy
4. Edit this defaultax object, which is the master page, in NotePad for example
5. Import the new modified master page back into the AOT
6. Run AXUPDATEPORTAL.EXE to deploy the edited master page