Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Simulating actions like New, Edit etc. by code
Miklos_Hollender
Member Posts: 1,598
Try this code: CLEAR(Item), Page.RUNMODAL(Page::"Item Card", Item); this thing (with FORM) in Classic would make you a new blank Item Card so that you can enter a new Item, in 2009 SP1 RTC gets a card with editing the first Item in your list. From the card you can go "New" again and another another, finally blank card, but it is confusing for the users.
I know in the worst case I can try temp tables. Still, any simpler ways? Why does the RTC think a blank record is not actually a new record but the first one in the list?
Possible use case if it is confusing: you have a customization that for every Item creates a record in a new table that shows statistical information for that item, gathered from other tables e.g. denormalizes the qty. per fields from the item unit of measure. You use this new list form, new table as your usual item list, but you still want to be able to let users create the normal, standard items from it, which will then be automatically processed and written back into this table.
I know in the worst case I can try temp tables. Still, any simpler ways? Why does the RTC think a blank record is not actually a new record but the first one in the list?
Possible use case if it is confusing: you have a customization that for every Item creates a record in a new table that shows statistical information for that item, gathered from other tables e.g. denormalizes the qty. per fields from the item unit of measure. You use this new list form, new table as your usual item list, but you still want to be able to let users create the normal, standard items from it, which will then be automatically processed and written back into this table.
0
Comments
- I can create a simulated New action (on another record than what is in the current list) by setting properties, but not code. The OnActon trigger will not run in 2009 SP1, this means automatic post-processing is not possible.
- Editing a record that is not in the current table should not be a problem however, because in the worst case even if the Page opens as View mode I can still click in the actions menu to go to edit mode. This must be acceptable.