Extension Unpublished/Uninstalled history required in BC Production environment

 There is a situation when someone can uninstall or unpublish any APP extension from the extension management in Production environment, there should be a feature available so that we should know who had uninstalled/unpublished that extension with their User name, Date and Time.

Vote to my question:

👍👍👍👍

Vote Here

README.md (Markdown) file in AL Code for writing your version control or project definition details

 Sometimes it can be easy if put all the information in one place related what we changed in our AL extension specially when there are multiple developers are working together,

use of Markdown file.

Is it best idea?

Yes, unlike a documentation trigger of each object, I would say this is the file README.md can be your whole Project's documentation trigger 👀 Called MarkDown

How to use it?

Just visit your AL code, create a new file and name it with a README.md.

see below 👇

• 2nd

• 3rd interesting part > Write your own documentation 👲

Start writing your version control or anything else here we go, and then click on Right hand corner button (Open Preview)

See how it looks like :

We have some cool features and market extension

Use me to check those out

Enjoy 👦👦👦

Can we choose the right environment before Publishing the BC App?

Yes, there is way we can define or modify our launch.json file in such a way that before publishing any custom app it ask me to the right environment to publish.

See below

Open the lanuch.json file from your app file.

Put the new configuration schema as many environment you have like I do.

In my case I do have two environment

1. Dev_Sandbox

2. Test_Sandbox

Save it and try to Publish or Download the symbol

So I am trying to download the symbol, as soon as you hit that command Command line will start show you which environment you want to choose so that you can download the symbol in same.

The same sandbox name we defined earlier start flowing here. 

Choose the one and enjoy :)

What is New in 20.5 BC?

 What is New in 20.5 BC?

See the details here

Upgrade to 20.5

Please note that new customers will automatically get the latest builds of Business Central (20.5). If you are an existing partner/customer, you will receive an email notification as soon as your environment has been upgraded.

Download the latest OnPrem version from here

Source 👆

Barcode Generator in Business Central 2

 

Generate a barcode in Business Central #BC of different type like EN128, EN8, EN39 or EN13 with custom code and without using any API, it can be used for lifetime without any subscription.

It also working with mobile scanner too. :)

Download the Git Here
#BC
#barcodelabels
#businesscentral
#barcodescanners

Prepare for major updates with preview environments for Wave 2 Busines Central 2022 (21)

 

Preview Environments for Business Central Wave 2 (2022, 21)

About one month before a major update, you can try out new functionality in preview environments. Preview environments are Business Central online sandbox environments that you create on a preview version of the application. When you create the new sandbox environment, choose the preview version marked as (Preview) from the version list. This way, you get a new sandbox environment with a preview version of the application.

Source - Documentation

you can start using preview environment for following purpose

Review the new functionality. Try it out, and begin training employees on the new features that are coming.

Validate your extensions.

Upload and install your extensions into the sandbox environments created on the preview version and run through the functionality. Verify that the customization continues to work and is compatible with the new version.

In rare cases, if you discover any changes required for your per-tenant extension to become compatible with the next release, apply the changes to your app, test it again on a sandbox environment running on a preview version. Then, if tests complete successfully, upload the app into your production environment, setting the Deploy to field to Next major version. This way, the compatible version of your app will be used when you schedule the upgrade of your production environment to the new major update once it becomes available.

Test the quality. If you run into issues related to the preview, please provide feedback on Collaborate.