Академический Документы
Профессиональный Документы
Культура Документы
Developer Guidelines
January 7, 2008
The information contained in this document represents the current view of Microsoft Corporation on the
issues discussed as of the date of publication. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft
cannot guarantee the accuracy of any information presented after the date of publication.
These test guidelines are for informational purposes only. MICROSOFT MAKES NO WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights
under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property
rights covering subject matter in this document. Except as expressly provided in any written license
agreement from Microsoft, the furnishing of this document does not give you any license to these
patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real
company, organization, product, domain name, email address, logo, person, place, or event is intended or
should be inferred.
Microsoft, Microsoft Dynamics, and Windows are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective
owners.
Introduction ....................................................................................................................... 5
About this Document ..................................................................................................................................................................... 5
Contents of the Developer Guidelines .................................................................................................................................... 5
Forms................................................................................................................................... 8
General Form Characteristics ...................................................................................................................................................... 8
List Forms ......................................................................................................................................................................................... 10
List Form Properties .................................................................................................................................................................10
Card Forms ...................................................................................................................................................................................... 11
Card Form Properties ..............................................................................................................................................................12
Reporting .......................................................................................................................... 23
Report Center ................................................................................................................................................................................. 23
End-user layout ..........................................................................................................................................................................23
Adding new reports .................................................................................................................................................................23
The goal of the document is to serve as a reference guide for developers/ISVs that are
building functionality for Microsoft Dynamics Entrepreneur to assure that these solutions
will have a consistent look and feel. For Microsoft Dynamics Entrepreneur Solution Add-
on Applications, this guide supersedes the corresponding Microsoft Dynamics NAV
documentation in case of contradicting information.
Menu structure
Form layouts
Centralized Maintenance for:
o Common Data
o Posting Groups
o Number Ranges
o Dimensions
Report Center
Company Set-up
Filter Area
Content Area
Summary Area
10
2 3
11
Note:
Please note that some form areas are optional (for example, the Resource Card does not
contain a summary area). This may cause some small differences in properties.
12
No Series Center
All Number Series are grouped in one central form called No. Series Center.
In case a localization or ISV-product contains additional No. Series, take the following
steps:
Property Value
Name MySubform
XPOS 3850
YPOS 990
Width 13750
Height 8250
HorzGlue Both
VertGlue Both
Visible No
Border No
SubformID No. Series Center Subform
13
Property Value
XPOS 440
YPOS Consecutive
Width 440
Height 550
Border No
Focusable No
Bitmaplist 35,39
SourceExpr (CurrFunctArea = DATABASE::"MyTable") AND
(CurrSubArea="Sub Area"::"MySubArea")
Property Value
XPOS 880
YPOS Consecutive
Width 2750
Height 550
FocusOnClick Yes
HorzAlign Left
BackTransparent Yes
Border No
5. Select the command button and add the following C/AL code to the OnActivate
trigger:
CurrFunctArea := DATABASE::"MyTable";
CurrSubArea := "Sub Area"::"MySubArea";
IF GET(CurrFunctArea, CurrSubArea) THEN;
CurrForm.MySubform.FORM.SetAreas(CurrFunctArea,
CurrSubArea);
CurrForm.MySubform.FORM.SetRecordFilter(TRUE);
CurrForm.UPDATE(FALSE);
6. Add the following line of C/AL Code to the function Initialize (located on the
Table Object No. Series Center):
MakeNoSeriesCenterRec(DATABASE::"MyTable", "Sub
Area"::"MySubArea");
14
Property Value
XPOS 17820
YPOS 990
Height 8250
Width 3520
HorGlue Right
VertGlue Both
Editable No
Focusable No
VertAlign Top
BackTransparent Yes
Border No
MultiLine Yes
SourceExpr GetText(“Text Type”::Description)
8. Running the form, you can use the No. Series Center->Translate button to add
a description for each licensed language.
15
Property Value
XPOS 440
YPOS Consecutive
Width 440
Height 550
Border No
Focusable No
Bitmaplist 35,39
SourceExpr CurrTableID=DATABASE::”MyTable”
16
Property Value
XPOS 880
YPOS Consecutive
Width 2750
Height 550
FocusOnClick Yes
HorzAlign Left
BackTransparent Yes
Border No
4. Select the command button and add the following C/AL code to the OnActivate
trigger:
CurrTableID := DATABASE::”MyTable”;
IF GET(CurrTableID) THEN;
ShowSubforms;
Property Value
Name MyTableSubform
XPOS 3850
YPOS 990
Width 13750
Height 8250
HorzGlue Both
VertGlue Both
Visible No
Border No
SubformID MySubformID
7. Delete the contents of the table Functional Area Table. (This requirement will
be deleted in a future release and is now still necessary to get the new elements
added to the form. When opening the form with an empty table an initialization is
activated automatically).
17
Property Value
XPOS 17820
YPOS 990
Height 8250
Width 3520
HorGlue Right
VertGlue Both
Editable No
Focusable No
VertAlign Top
BackTransparent Yes
Border No
MultiLine Yes
SourceExpr GetText(“Text Type”::Description)
9. Running the form, you can use the Common Data->Translate button to add a
description for each licensed language.
18
Because the number of Dimensions within Basic Dimensions is limited to two there is no
description how to add additional dimensions.
19
In case a new posting groups need to be added, take the following steps:
Property Value
XPOS 440
YPOS Consecutive
Width 440
Height 550
Border No
Focusable No
Bitmaplist 35,39
SourceExpr CurrTableID=DATABASE::”MyTable”
20
Property Value
XPOS 880
YPOS Consecutive
Width 2750
Height 550
FocusOnClick Yes
HorzAlign Left
BackTransparent Yes
Border No
4. Select the command button and add the following C/AL code to the OnActivate
trigger:
CurrTableID := DATABASE::”MyTable”;
IF GET(CurrTableID) THEN;
ShowSubforms;
Property Value
Name MyTableSubform
XPOS 3850
YPOS 990
Width 13750
Height 8250
HorzGlue Both
VertGlue Both
Visible No
Border No
SubformID MySubformID
7. Delete the contents of the table Functional Area Table. (This requirement will
be deleted in a future release and is now still necessary to get the new elements
added to the form. When opening the form with an empty table an initialization is
activated automatically).
21
Property Value
XPOS 17820
YPOS 990
Height 8250
Width 3520
HorGlue Right
VertGlue Both
Editable No
Focusable No
VertAlign Top
BackTransparent Yes
Border No
MultiLine Yes
SourceExpr GetText(“Text Type”::Description)
9. Running the form, you can use the Posting Group->Translate button to add a
description for each licensed language.
22
Report Center
All reports within Microsoft Dynamics Entrepreneur are grouped in the Report Center.
Like all other centers functional areas are used to group reports.
End-user layout
End User can access all reports from the Report Center form. The right-hand part of the
form displays the most essential layout elements of the marked report.
1. Open the Report Center with a development license and a number of additional
buttons will be visible on the form:
23
4. Select Report Copy in the Report Center form to copy a report from one
functional area to another functional area.
24
Note:
Reports can also be run from list- and card forms of the main entities. In that situation
only reports are shown that are directly related to that specific entity. Filter criteria for this
is the table ID of that entity. This ID can be filled in for each separate report within the
report Center as shown below.
25
Every module/functional area has a separate tab on which the relevant parameters can
be maintained.
Notes:
Only fields related to functionality that is part of Microsoft Dynamics Entrepreneur
must be made available on the respective tabs.
In case of adding a new functional area that requires set up, a new tab should be
added for this as well.
Although users can maintain the set up themselves the goal is to have the values
filled in automatically during initializing the company (using the Implementation
Wizard).
26