Mandatory fields on forms
A common customer request is mandatory fields and I usually recommend a solution where a test is made at posting time. This seems to be “the Navision way” and I see a value in keeping things consistent.
Once in a while though, there is a real need for a field to be mandatory from the moment it is inserted.
This is a simple solution for records that does not use no. series or other special logic for creating the primary key.
- Set the NotBlank property on the field to Yes
- Add a FieldName.TESTFIELD to the table OnInsert trigger.
- Set the DelayedInsert property on the form to Yes
No guarantees, just something had forgotten about and needed again the other day.
The last error mes½D§¤@
Posted by askeholst in Dynamics NAV on October 1, 2009
Got this error message from the Job Queue Transaction List at a customer site. Some kind problem occurred with the SAN that the application server is on, seemingly not only causing the write to fail but even the error message itself!
Shared items- Alex's Soapbox: Patterns of Failure Alex Papadimoulis
- Extended NAV/SQL Database Hardening Jörg A. Stryk
- Why Windows Azure is the Future of Microsoft (and Enterprise Software as Well) ematters
- Warehousing Improvements in NAV 2009 SP1 navblog
- Feature Enhancements Documents for Microsoft Dynamics NAV 2009 navblog
- Application Test Toolset for Microsoft Dynamics NAV 2009 SP1 sgrubov
- Sweet State Machine DSL in "M" Chris Sells
- Creating a web service manually, the importance of the name you give it, and a few small things to remember Lohndorf
- Custom Control for Reporting Services Reports David Roys
- Running Code on the Client without deploying COM objects freddyk