BC: PageExtension - placing the standard field from standard group to custom group

Damjan
Member Posts: 94
Hi All,
How to properly move standard field to custom group?
I am designing page as pageextension of standard page "Create Interaction". I know how to display custom fields on a page, but I just don't understand how to move standard field from standard group to new custom group that I placed on the page.
placing the field: "Cost (LCY)" on the pageextension of standard page "Create Interaction" is not accepted, since it is already placed on the standard page "Create Interaction".

How to properly move standard field to custom group?
I am designing page as pageextension of standard page "Create Interaction". I know how to display custom fields on a page, but I just don't understand how to move standard field from standard group to new custom group that I placed on the page.
placing the field: "Cost (LCY)" on the pageextension of standard page "Create Interaction" is not accepted, since it is already placed on the standard page "Create Interaction".

0
Best Answer
-
You can move "Cost (LCY" with code like:
pageextension 50000 "XXX" extends "XXXX" { layout { movefirst(General;"Balance (LCY)") } }
or you can create the field, and set a different name like:pageextension 50000 "XXX" extends "XXXX" { layout { addfirst(General) { field("PREFIX-Balance (LCY)"; Rec."Balance (LCY)") { ApplicationArea = All; } } } }
Both ways have Pros and Cons,
Moving base app fields:
Pros:
- Do not add more load to page
- Field is not display multiple time
- Page look cleaner
Cons:
- If MS remove the field from the page, your extension will break
For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.0
Answers
-
You can move "Cost (LCY" with code like:
pageextension 50000 "XXX" extends "XXXX" { layout { movefirst(General;"Balance (LCY)") } }
or you can create the field, and set a different name like:pageextension 50000 "XXX" extends "XXXX" { layout { addfirst(General) { field("PREFIX-Balance (LCY)"; Rec."Balance (LCY)") { ApplicationArea = All; } } } }
Both ways have Pros and Cons,
Moving base app fields:
Pros:
- Do not add more load to page
- Field is not display multiple time
- Page look cleaner
Cons:
- If MS remove the field from the page, your extension will break
For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.0 -
I'll use second approach. Tnx0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions