36 lines
No EOL
9.9 KiB
XML
36 lines
No EOL
9.9 KiB
XML
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>alguidelines.dev - Business Central Design Patterns – NAV Patterns Archive</title><link>https://alguidelines.dev/docs/navpatterns/</link><description>Recent content in NAV Patterns Archive 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/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Patterns</title><link>https://alguidelines.dev/docs/navpatterns/patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/patterns/</guid><description>
|
||
<div class="alert alert-warning" role="alert">
|
||
<h4 class="alert-heading">Warning</h4>
|
||
Please note that these patterns may not be up-to-date with the patterns for AL and Business Central Development.
|
||
</div></description></item><item><title>Docs: 2. Anti-Patterns</title><link>https://alguidelines.dev/docs/navpatterns/2-anti-patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/2-anti-patterns/</guid><description>
|
||
<p>Some of the software development practices, had <strong>not</strong> stood the test of time. Despite that, some are still being used today by developers everywhere.</p>
|
||
<p>&ldquo;An <strong>anti-pattern</strong> (or <strong>antipattern</strong>) is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive&rdquo; (from <a href="http://en.wikipedia.org/wiki/Anti-pattern">Wikipedia</a>)</p>
|
||
<p>Since almost the beginning of the NAV Design Patterns project, we talked about documenting the anti-patterns - but never found the time. Until, spontaneously, the April 1st 2015 article had practically wrote itself in a couple of hours, with priceless contributions coming from Andreas, Elly, Nikola - and last but not least, waldo.</p>
|
||
<p>Best regards,</p>
|
||
<p>Bogdana Botez</p></description></item><item><title>Docs: 3. CAL Coding Guidelines</title><link>https://alguidelines.dev/docs/navpatterns/3-cal-coding-guidelines/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/3-cal-coding-guidelines/</guid><description>
|
||
<p>We&rsquo;ve decided to publish our current C/AL coding guidelines. They are actual, as per January 2015 when this is published (but might fall out of sync as time goes by).</p>
|
||
<p>You can also <a href="https://blogs.msdn.microsoft.com/nav/2015/01/09/cal-coding-guidelines-used-at-microsoft-development-center-copenhagen" title="download the C/AL coding guidelines as pdf">download the C/AL coding guidelines as pdf,</a> all in one document. In contrast, on this wiki, the coding guidelines are published individually. The reason is: give you the chance to comment and share your oppinion on each one. Thanks to <a href="https://alguidelines.dev/members/waldo/default.aspx" title="waldo">waldo</a> for this idea and for helping out.</p>
|
||
<p>The guidelines are debatable - and it is good when they are generating debate. There is variation of opinion on the rules at Microsoft too. The plan is to simply expose what we use now. And more important, to say that guidelines could be used. Debate on individual guidelines can become heated for any programming language, but the benefit of using some guidelines stays.</p>
|
||
<p>For us, those guidelines are enforced at check-in time - we are using a tool which verifies and only allows compliant check-ins. While this tool is internal and not ready to publish, we had anyways decided to open up and present the rules we use to the community, as inspiration.</p>
|
||
<p>Question: Since we&rsquo;re having the guidelines, how come there is still C/AL code in NAV which doesn&rsquo;t respect them?</p>
|
||
<p>Answer: all new C/AL code is bound to follow the guidelines (else it cannot be checked-in). However, the code that existed before the rules - it does not. We had done cleanup in a certain degree. Now we&rsquo;re gradually improving the old code base as we visit various objects in order to add new functionality, however chances are that code we didn&rsquo;t touch in a long time had remained in its old form.</p>
|
||
<p>We&rsquo;re looking forward to your comments. Where you can, do provide concrete examples of the alternatives, Good and Bad.</p>
|
||
<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;">
|
||
<iframe src="https://www.youtube.com/embed/z6skKy0pkmU" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" allowfullscreen title="YouTube Video"></iframe>
|
||
</div></description></item><item><title>Docs: (OLD) Get Involved</title><link>https://alguidelines.dev/docs/navpatterns/4-get-involved/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/4-get-involved/</guid><description>
|
||
<h2 id="reminder-this-is-an-archive-of-the-patterns-site-this-information-is-not-current"><strong>Reminder, this is an ARCHIVE of the Patterns site, this information is not current.</strong></h2>
|
||
<p><strong>Spread the info</strong></p>
|
||
<p>NAV Design Patterns are excellent materials for training and knowledge transfer. In your company, you can help new developer get to speed with NAV by recommending them to read and then present to the team one of the most common patterns: <a href="https://alguidelines.dev/navpatterns/1-patterns/no-series/" title="No. Series">No. Series</a>, <a href="https://alguidelines.dev/navpatterns/1-patterns/singleton/singleton-table/setup-table/" title="Setup Table">Setup Table</a> and definitely <a href="https://alguidelines.dev/navpatterns/1-patterns/hooks/" title="Hooks">Hooks </a>which will be a great investment in reducing your upgrade time. The more experienced developers can read directly the newer patterns, like <a href="https://alguidelines.dev/navpatterns/1-patterns/implementation-of-surrogate-keys-using-autoincrement-pattern/">Surrogate Key</a>, <a href="https://alguidelines.dev/navpatterns/1-patterns/easy-update-of-setup-or-supplementary-information/">Easy Update</a>, <a href="https://alguidelines.dev/navpatterns/1-patterns/totals-and-discounts-on-subpages-sales-and-purchases/">Totals on Subpages</a>, <a href="https://alguidelines.dev/navpatterns/1-patterns/queries/use-queries-to-replace-nested-loops/">Using Queries instead of nested loops</a> etc.</p>
|
||
<p><strong>Become a NAV Design Pattern author</strong></p>
|
||
<p>You have a pattern that you have used successfully? You have ideas on new patterns? You&rsquo;ve found some existing design patterns which are used in the product but nobody (except a few) knows how it works, but you find it worth it to explain it for the NAV C/AL developers out there?</p>
|
||
<p>Send your pattern idea to <a href="https://alguidelines.dev/members/bogdana-botez/default.aspx">Bogdana Botez</a> as a private message on the community webpage. Once your first pattern is ready, we will review it as a team, and when signed off, you get author permissions on the Wiki site and from then on, you can continue publishing and editing existing patterns. However, only publish on the Wiki materials that we had signed-off (we don&rsquo;t have moderation capabilities yet, so we count on each author to only make meaningful/agreed changes).</p>
|
||
<p>You and your company also get credit by being mentioned on the pattern and also on our patterns authors page.</p>
|
||
<p>Once you have the idea, writing it down shouldn&rsquo;t take long. You will be helped by adopting <a href="https://alguidelines.dev/navpatterns/4-get-involved/template-for-writing-nav-design-patterns/">the template </a>that we&rsquo;ve used.</p>
|
||
<p><strong>Remember the rules</strong></p>
|
||
<p>When handling design patterns, content quality is critical. We are trying our best to only publish content that is correct, relevant and has been reviewed by multiple developers. Therefore, we review and sign-off all patterns before publishing them (except for the videos made prior to 2015). All text content found on this Wiki and on the NAV Team Blog has been through one, usually multiple iterations of review. If you find something to correct, please comment on the pattern or contact <a href="https://alguidelines.dev/members/bogdana-botez/default.aspx" title="Bogdana Botez">Bogdana Botez</a>, and we will review and update it.</p>
|
||
<p>We are working on creating a set of rules, which would help keeping the content clean and the project on the correct track. <a href="https://alguidelines.dev/navpatterns/4-get-involved/code-of-conduct/" title="Find the rules here">Find the rules here</a>.</p></description></item><item><title>Docs: Related Links</title><link>https://alguidelines.dev/docs/navpatterns/related-links/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/navpatterns/related-links/</guid><description>
|
||
<p>Find below some related NAV Design Patterns links.</p>
|
||
<p><a href="http://blogs.msdn.com/b/nav/archive/tags/patterns/" title="MSDN NAV Team Blog - posts about patterns">MSDN NAV Team Blog - posts about patterns</a></p>
|
||
<p><a href="http://mibuso.com/dlinfo.asp?FileID=1573" title="NAV Application Design slides ">NAV Application Design slides </a>from NAV TechDays conference in Antwerp, 2013</p>
|
||
<p><a href="http://mibuso.com/dlinfo.asp?FileID=1556" title="NAV Application Design movie">NAV Application Design movie</a> from NAV TechDays conference in Antwerp, 2013</p>
|
||
<p><a href="http://mibuso.com/dlinfo.asp?FileID=1568">NAV&rsquo;s Secret Code: Design Patterns of Today and Tomorrow</a> slides from NAV TechDays conference in Antwerp, 2013</p></description></item></channel></rss> |