Skip to main content

How To Create Forms in Enterprise Portal

1. Open Microsoft Dynamics AX.
2. Open the AOT.
3. Right-click on the Data Sets node and choose New Data Set.
4. Right-click on the newly added data set and choose Properties.
5. In the property sheet rename the new Data Set to SampleCustomers.
6. Expand SampleCustomers.
7. Right-click the Data Sources node and choose New Data Source.
8. Right-click the new Data Source and choose Properties.
9. In the property sheet set the Table property to CustTable.
10. In the property sheet set the Name property to CustTable.
11. In the property sheet set the InsertIfEmpty property to No.

  • Create a Web Project
1. Open Microsoft Visual Studio 2008.
2. Under the File menu choose New and then Web Site.
3. Choose Visual C# as the Language – note that only C# is supported.
4. Choose Dynamics AX Web Project as the template.
5. Enter SampleBasicForm as the project name.
6. Click OK when finished.
  • Create a User Control and Add it to the AOT
1. In Visual Studio add a new File under File then New File.
2. Choose Visual C# as the language.
3. Choose Dynamics AX User Control under the My Templates Section.
4. Enter SampleBasicForm.ascx as the name.
5. Click Add when finished.
6. In the Solution Explorer, right-click on the new user control, SampleBasicForm.ascx, and select Add to AOT.

  • Add a Form to Your User Control
Forms in Enterprise Portal are used to display and edit record information. They consist of three different controls, an AxDataSource, an AxForm, and an AxGroup. The AxDataSource is used to interact with data. The AxForm is a container for the form entity. The AxGroup will reference and display fields
from the data. The specific record information to display is retrieved from the external context (information passed through the URL).

1. In Visual Studio in the Solution Explorer, right-click the user control and select View Designer.
2. Locate the Microsoft Visual Studio 2008 Toolbox under View then Toolbox.
3. Find and expand the Dynamics AX section.
4. Drag-and-drop an AxDataSource onto the design.
5. Click on the arrow in the upper right-hand corner of the AxDataSource and set the DataSet Name    property to SampleCustomers. This can also be done through the properties pane.
6. Right-click on the AxDataSource and choose Properties.
7. Rename the new AxDataSource to Customers_DS by changing the (ID) property to Customers_DS.
8. Find the AxForm control in the toolbox under View and then Toolbox.
9. Drag-and-drop the AxForm onto the design.
10. Right-click on the AxForm and choose Properties.
11. Rename the AxForm’s ID to SampleCustomers by changing the (ID) property.
12. Set the DataSourceID property to Customers_DS.
13. Set the DataMember property to CustTable_Current.
14. Find the AxGroup control in the toolbox under View and then Toolbox.
15. Drag-and-drop the AxGroup onto the AxForm.
16. Right-click on the AxGroup and choose Properties.
17. In the Fields property for the AxGroup, click the … icon.
18. Add AccountNum, Name and Address from Available Fields by double-clicking or selecting each item and clicking Add Field.
19. Press OK to save.
20. Click the Save icon on the Visual Studio toolbar to save your project.

  • Testing Your User Control To Test Through Microsoft SharePoint Services
1. Navigate to your Microsoft Dynamics AX Enterprise Portal web site.
2. Click on Site Actions and select Create.
3. Click on the Web Part Page link.
4. Choose a Name, Template, and the Document Library Enterprise Portal.
5. Click the Create button.
6. If the page is not in Edit Mode, click Site Actions and select Edit.
7. In one of the web page’s sections click the Add a Web Part bar.
8. Check Dynamics User Control Web Part and select Add.
9. On the new web part, click edit and select Modify Shared Web Part.
10. Set the Managed content item property to your user control, SampleBasicForm.
11. Click OK.
12. Under the Site Actions menu click the link Exit Edit Mode.
13. Minimize the web browser.
14. Locate and open the web.config file for the SharePoint site. (ex: C:\Inetpub\wwwroot\wss\VirtualDirectories\80)
15. Locate the compilation section and set the debug property to true



16. Open your Microsoft Visual Studio 2008 SampleBasicForm project.
17. From the menu choose Debug and select Attach to Process.
18. Select the w3wp.exe process for the SharePoint site and click Attach.
19. In Visual Studio’s Solution Explorer right-click your control and choose View Code.
20. Add breakpoints to the code where needed.
21. Maximize the open web browser and refresh the SharePoint site.
22. When finished debugging, set the debug attribute in the web.config file back to false.

  • To Test Through Microsoft Visual Studio 2008
1. In Visual Studio in the Solution Explorer, right-click the project node and select Import Style Sheets.
2. In the Solution Explorer, right-click the AxWebPartPage.aspx page and select View Designer.
3. In the design under Body, locate dynamics:AxUserControlWebPart1. It is the second box containing Untitled under the Body.
4. Right-click dynamics:AxUserControlWebPart1 and choose Properties.
5. Set the Dynamics AX Managed Web Content Item property to your user control, SampleBasicForm.
6. Save your control.
7. In the Solution Explorer right-click your SampleBasicForm control and choose View Code.
8. Add breakpoints to the code where needed.
9. In the Solution Explorer, click on the AxWebPartPage.aspx so it is selected.
10. Click the green arrow on the toolbar to build and run the solution.

Comments

Popular posts from this blog

Process of Sales order in Technical terms in D365Fo

 ðŸ”¥ Sales Order Technical Flow in D365FO (Creation → Confirmation → Picking → Packing Slip → Invoice → Accounting) 1. Sales Order Creation Tables SalesTable → SO header SalesLine → SO lines CustTable → Customer master InventDim / InventDimCombination → Dimensions InventTable / EcoResProduct → Item master Framework Classes SalesTableType / SalesLineType Responsible for validation, defaulting, creation logic Key Methods SalesTable.initValue() SalesLine.initFromSalesTable() SalesTable.validateWrite() SalesLine.validateWrite() Events (Extensions) SalesTableType.createSalesTable() SalesLineType.createSalesLine() 2. Reservation (Optional) If reservation is done: Tables InventTrans (Reservation status) InventReservation Classes InventUpd_Reservation InventTransReservation Reservations impact picking and inventory availability. 3. Sales Order Confirmation Confirms order and freezes price/quantity. Posti...

Top 200 Q&A in D365FO Technical

  SECTION 1 — X++ BASICS (10 Q&A) 1. What is X++? A proprietary object-oriented language used in Dynamics 365 Finance & Operations for business logic, similar to C# but integrated with D365 runtime. 2. What is a TableBuffer? It is an in-memory object referencing a table. Example: CustTable custTable; 3. What is difference between select and select firstonly ? select → returns all matching rows firstonly → returns only the first matched row 4. What is ttsbegin & ttscommit ? Used to wrap database transactions; ensures atomicity. 5. Can we write SQL queries directly in X++? No. X++ uses a database-abstracted select statement. 6. What is a container? A collection datatype used to store mixed data types. 7. Difference between container and map? Map stores key-value pairs; container is indexed and immutable. 8. What is a temp table? A table that stores data temporarily in memory or database depending on property. 9. What is recursion in X++? A method c...

Process of Purchase order in Technical terms in D365Fo

  Purchase Order Technical Flow in D365FO (Step-by-Step) (From creation → approval workflow → posting → product receipt → invoice → accounting) 1. Purchase Order Creation Tables involved PurchTable → PO header PurchLine → PO lines VendTable → Vendor master InventDim / InventDimCombination → Item dimensions EcoResProduct / InventTable → Item master Classes / Framework PurchTableType / PurchLineType Framework that controls creation, validation, defaulting. Key methods PurchTable.initValue() PurchLine.initFromPurchTable() PurchTable.validateWrite() PurchLine.validateWrite() Events (Extension points) PurchTableType.createPurchTable() PurchLineType.createPurchLine() 2. Purchase Order Confirmation Document Status update PurchTable.DocumentState → Confirmation PurchParmBuffer tables used for versioning. Posting Class PurchFormLetter_Confirm Called internally via PurchFormLetter::construct(DocumentStatus::Co...