DynamicsSubs

   Imagine a situation where you need to add controls to a form, on run time. You have a dynamic source, (example, a booking app, where user would keep on adding newer choices, and you need to bring them to your form as checkboxes -- there is no prefixed set of choices beforehand: it would vary), and you need to add controls to your form by looping through your datasource. A cool way of doing this is to use: Form build controls. For example, for the above situation, you can add FormBuildCheckBoxControl. Or if you need to fill in into a combobox control, you might use FormBuildComboBoxControl.    So what are FormBuild controls actually? For example, the FormBuildComboBoxControl class lets you create, read, update, and delete X++ code and metadata. It behaves as if you are still in designing the UI and can keep on changing the metdata of various controls, while  actually  you are running the code. How to add a FormBuild control: The following code shows that ...

  In a world where we live by action, automation and speed, Azure Biceps are an awesome way to expeidate your deployments. Biceps are new normal and monograms of infrastructure-As-Code, where you can manipulate your resource creation by feeding in parameters, inputs and varying conditions through Azure CLIs. Confused? Let me bring up the definition of Azure Biceps, from Microsoft's definition:  Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to repeatedly deploy your infrastructure. Your resources are deployed in a consistent manner .  You cane create any resource, resources -- any number of them, simply mainitaining their defintions on simple module based files and invoking their deployments through Azure CLI based commmands. As compared ARM templates: Bicep syntax reduces that complexity...

     You must have heard the term  Batch Data pipeline  and ' ETL ' interchangeably. But that's alway s not true: A Data pipeline is an automated process which enables moving data from one system to another. This data might or might not be transformed, and it maybe processed synchronously, instead of assynch batch execution or could be both. ETL is extraction, Transform and Load which extracts data from one source system, transforms and then loads to another target system (a database/ data warehuse). This write up is going to show you how to preform cleaning, transformation of data from a source system and save it to a target Database, step by step. We can start by creating a Azure Synapse Analtics Workspace: https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started-create-workspace A point to ponder: Please don't forget to check the entry under: While going through the above tutorial link. I created my own workspace and named it as  neos-worksp...

  We all know there is a drastic change in licensing, as introduced as a part of architectural change in PU39. T he official documentation mentions support for SHA1 until was till February 2024, and then you can migrate to SHA256. When generating a license using the AxUtil tool, you need to use signature version 2 or leave this field blank to generate a new license using SHA256 . This change applies to new versions starting from 10.0.39. You need to upgrade the system version to implement feature updates. Typically, software updates and features are designed for specific versions, and it is recommended to upgrade to the target version. You need keep in mind few things, while applying the licenses you get from your ISV partners. Option A:  When you get the patch (the patch ZIP file, compatible with PU39) from your ISV partner, make sure you do this, before you apply the patch to your environments. Step 1: You need to get the license files from your partner first. They are typic...