deploy: d7a7d2459a
This commit is contained in:
JeremyVyska
parent
34af3362da
commit
2d866c6316
732 changed files with 136202 additions and 67025 deletions
337
docs/navpatterns/4-get-involved/index.xml
Normal file
337
docs/navpatterns/4-get-involved/index.xml
Normal file
|
|
@ -0,0 +1,337 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>alguidelines.dev - Business Central Design Patterns – (OLD) Get Involved</title><link>https://alguidelines.dev/docs/navpatterns/4-get-involved/</link><description>Recent content in (OLD) Get Involved on alguidelines.dev - Business Central Design Patterns</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/docs/navpatterns/4-get-involved/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Code of Conduct</title><link>https://alguidelines.dev/docs/navpatterns/4-get-involved/code-of-conduct/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/4-get-involved/code-of-conduct/</guid><description>
|
||||
<p>Find below the rules to be used when disseminating or relating to the NAV Design Patterns.</p>
|
||||
<ol>
|
||||
<li>Only use materials published in text on the NAV Design Patterns Wiki site. If you received from us, any unpublished materials, please observe that they are subject to change and have not been approved for external use.</li>
|
||||
<li>When referencing a NAV Design Pattern, you must remember to also reference its author and company where the author is employed. You will find the author and his/her company at the beginning of each pattern, under the title.</li>
|
||||
<li>When referencing a NAV Design Patterns project, you must make it clear that this is a community project, driven by Microsoft, with multiple developers involved from both Microsoft and the community.</li>
|
||||
<li>When using published text content of NAV Design Patterns, do not alter the text in any way that was published on the Wiki site, unless is has been reviewed by the patterns team and signed off by someone at Microsoft in writing.</li>
|
||||
<li>If you have other materials which have not received explicit signoff in writing from me, where I have specifically stated that they are valid design patterns ready for publishing, please do not name them &ldquo;NAV Design Patterns&rdquo; (or anything similar). You are free to use your own content, but do not associate it in any way with NAV Design Patterns unless it is signed off in writing.</li>
|
||||
<li>If you do choose to use your own content, you must make it clear that it is not a NAV Design Pattern.</li>
|
||||
</ol></description></item><item><title>Docs: Patterns Authors</title><link>https://alguidelines.dev/docs/navpatterns/4-get-involved/patterns-authors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/4-get-involved/patterns-authors/</guid><description>
|
||||
<p>This is the list of people that have been part of the NAV Design Patterns team. If you would like to join the project follow the instructions provided on <a href="https://alguidelines.dev/navpatterns/4-get-involved/">Be a NAV Pattern Author</a> page.</p>
|
||||
<p>Project administrator: <a href="https://alguidelines.dev/members/bogdana-botez/default.aspx" title="NAV Design Patterns project administrator">Bogdana Botez</a>.</p>
|
||||
<p>Authors (in alphabetical order):</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Abshishek Ghosh, Microsoft (4 patterns)</p>
|
||||
<ul>
|
||||
<li>Using Query Objects to Detect Duplicates</li>
|
||||
<li>Blocked Entity</li>
|
||||
<li>Single-Record (Setup) Table</li>
|
||||
<li>Temporary Dataset Report</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anders Larsen, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Easy Update of Setup or Supplementary Information</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Andreas Moth, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-pattern: Reusable bugs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Bogdan Sturzoiu, Microsoft (4 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Feature Localization for Data Structures</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Copy Document</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Using C/AL Query Objects Instead of Nested Loops</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Data-Driven Blocked Entity</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Bogdana Botez, Microsoft (18 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Silent File Upload and Download</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Standard Journal</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>No. Series</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Data Model Proxy</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Journal Error Processing</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Journal Template-Batch-Line</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Multilanguage Application Data</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>SELECT DISTINCT using Queries</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-patterns: reusable bugs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Sensitive Data Encapsulation</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Data Encryption</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Single Point of Access</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Masked Text</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>SSL in NAV</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Singleton</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Singleton Codeunit</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-Patterns in NAV Upgrade</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Cue table</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Carlos Raul Garcia, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-Patterns in NAV Upgrade</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Ciprian Iordache, Microsoft (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Activity Log</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Totals and Discounts on Subpages (Sales and Purchases)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>David Bastide, Microsoft (3 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Notification Lifecycle Management pattern</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Data Migration Façade</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Extending the Role Center Headlines</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Elly Nkya, Microsoft (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Singleton Table</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-patterns: reusable bugs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Eric Wauters (waldo), iFacto, PRS (6 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Hooks</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Posting Routine - Select Behaviour</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Variant Facade</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Argument Table</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Discovery Event</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-patterns: reusable bugs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Gary Winter, agiles (1 pattern)</p>
|
||||
<ul>
|
||||
<li>Variant Façade</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>Henrik Langbak, Kim Ginnerup, Bording Data A/S (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Currently Active Record</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Released Entity</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Jan Hoek, IDYN (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Conditional Cascading Update</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Setup Specificity Fallback</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Jesper Schulz, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Error Message Processing, part I</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Martin Dam, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Multi-File Download</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Mike Borg Cardona, Microsoft (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Creating URLs to NAV Clients</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Mostafa Balat, Microsoft (3 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>.NET Exception Handling</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Cached Web Service Calls</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Try Method</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Nikola Kukrika, Microsoft (7 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Totals and Discounts on Subpages (Sales and Purchases)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Create Data from Templates</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Argument Table</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Instructions in UI</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Creating Custom Charts</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Variant Façade</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Anti-patterns: reusable bugs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Nikolai L&rsquo;Estrange, from TVision Technology Ltd. in the UK_<br>
|
||||
_ (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Observer</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Cross Session Events</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Raed Selim, Microsoft (1 pattern)</p>
|
||||
<ul>
|
||||
<li>Product Name</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>Soumya Dutta (2 patterns)</p>
|
||||
<ul>
|
||||
<li>In-context notifications</li>
|
||||
<li>Data Migration Façade</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>Søren Klemmensen, 360 Visibility, PRS (2 patterns)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Master Data</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Surrogate Key</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Tim Grant, Trendmicro (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Read Once Setup Record</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Report Selector (this pattern was started by 2 workgroups by multiple authors, but finalized and corrected by Tim).</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Xavier Garonnat, knk Ingénierie (1 pattern)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Document</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>They have also invested their time and energy in this project:</p>
|
||||
<ul>
|
||||
<li>Eva Dupont, Microsoft - our publisher on MSDN NAV Team Blog.</li>
|
||||
<li>Kurt Juvyns, Microsoft - coordinator of pattern videos</li>
|
||||
</ul>
|
||||
<p>Pattern evangelists:</p>
|
||||
<ul>
|
||||
<li>Eric Wauters (waldo), iFacto, PRS</li>
|
||||
<li>Gary Winter, agiles, PRS</li>
|
||||
<li>Mark Brummel, Brummel Dynamics Services, PRS</li>
|
||||
<li>Mike Doster, Mergetool</li>
|
||||
<li>Søren Klemmensen, 360 Visibility, PRS</li>
|
||||
</ul>
|
||||
<p>And last but not least, we have collaborated with Plataan who hired Eric Wauters from ifacto and Mark Brummel from Brummel Dynamics Services and PRS, to publish on video some of our patterns.</p></description></item><item><title>Docs: Template for writing Nav Design Patterns</title><link>https://alguidelines.dev/docs/navpatterns/4-get-involved/template-for-writing-nav-design-patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/4-get-involved/template-for-writing-nav-design-patterns/</guid><description>
|
||||
<p>This is a guideline, some parts are optional (if there&rsquo;s no content, remove the whole paragraph).</p>
|
||||
<p>&lt;<em>Your name here in italics, plus your company name</em>&gt;</p>
|
||||
<h2 id="pattern-title"><strong>&laquo;Pattern Title&gt;&gt;</strong></h2>
|
||||
<p>Short, descriptive and easy to remember.</p>
|
||||
<h2 id="pattern-logo"><strong>Pattern Logo</strong></h2>
|
||||
<p>Black &amp; white, no text on it.</p>
|
||||
<p><a href="PatternLogo.png"><img src="PatternLogo.png" alt=" "></a></p>
|
||||
<p><strong>Context</strong>: Sets the stage where the pattern takes place. 1-2 sentences.</p>
|
||||
<p><strong>Problem</strong>: What happens before this pattern is used? How can it go wrong? 1-5 lines.</p>
|
||||
<p><strong>Forces:</strong> (explain why the problem is difficult to solve; state the considerations that must be taken into account when choosing a solution to a problem)</p>
|
||||
<ul>
|
||||
<li>&laquo;**Force 1: **short description (What is the impact of not using this pattern? Or using only partially?) &gt;&gt;</li>
|
||||
<li>&laquo;**Force 2: **short description &gt;&gt;</li>
|
||||
<li>&hellip;</li>
|
||||
</ul>
|
||||
<p><strong>Solution:</strong> 1-2 sentences. The full description will come below.</p>
|
||||
<p>&laquo;Solution descriptions&gt;&gt;</p>
|
||||
<p>&laquo;Diagrams. Please add numbers and captions to both figures and tables&gt;&gt;</p>
|
||||
<p><strong>Usage</strong>: &laquo;short usage description&gt;&gt;</p>
|
||||
<p>&laquo;Examples&gt;&gt;</p>
|
||||
<p>&laquo;Where it&rsquo;s used in Dynamics NAV&gt;&gt;</p>
|
||||
<p><strong>Benefits:</strong></p>
|
||||
<ul>
|
||||
<li>**&laquo; Benefit 1: **solves Force 1, short description&gt;&gt;</li>
|
||||
<li>**&laquo; Benefit 2: **solves Force 2, short description&gt;&gt;</li>
|
||||
<li>&hellip;</li>
|
||||
</ul>
|
||||
<p><strong>Consequences:</strong></p>
|
||||
<ul>
|
||||
<li>**&laquo;Consequence 1: **are there any drawbacks? Is there anything the developer needs to be aware of when implementing this pattern? Any known limitations? <strong>&gt;&gt;</strong></li>
|
||||
<li><strong>&hellip;</strong></li>
|
||||
</ul>
|
||||
<p><strong>List of references</strong></p></description></item></channel></rss>
|
||||
Loading…
Add table
Add a link
Reference in a new issue