Hi! My name is Diana Birkelbach and I’m a developer, working at ORBIS AG . Together with the team we develop generic components and accelerators for Dynamics 365 and Power Platform.


One of the biggest accomplishments are the Microsoft Most Valuable Professional Award (MVP) in Business Applications for 2021.  

You can also find me in the Power Platform Community Forum, where I’m part of the Power Platform Community Super User Program (Appstronaut) 

I started with web development with ASP (VB) in the old days before the .NET was there. For better performance I used a lot of JavaScript and TSQL. Later on I moved to ASP.NET and C#.

I developed for Dynamics 365 from the beginning, starting with the version 1.1 (back then Microsoft CRM). In that old days we had to use triggers on the SQL (since there were no PlugIns, or Callouts as they were called in CRM 3) and starting with CRM 3.0 I worked to our first generic Editable Grid. In CRM 4.0 times I made a new generic and this time pure HTML-based Editable Grid, together with a Core-Library for working with the Dynamics 365. I think it was that time when I started to become “Miss Metadata”, since I tried to work around the performance Issues with Metadata as came up with several solutions for caching it for the client script.

I worked also with Azure (connected to Dynamics 365), but lately I focus on front end development: I love working with HTML, CSS, JavaScript ES6+, Typescript, React & Redux & React Hooks.

I’ve got to know a little about the Power Platform in Spring 2019, and as soon the PowerApps Component Framework (PCF) preview was released, it become my new love. Since then I try to get it to know better, write blogs to help others to understand it. When I have some time , I try to make some open-source PCFs. 

18 thoughts on “About

Add yours

  1. Hi Diana
    I have been reading your blog for a while now and your knowledge is amazing.
    I don’t know if you can help but I have a web resource I need to either remake into a PCF or update its code so that it will continue to work in the future.
    is this something you might be able to give me some advice on doing?

    1. Thank you for the nice words! 🙂
      If I would need to remake a HTMLWebResource I would go with a PCF. Maybe a lot can be reused. But also a design containing a combination of Custom Pages and PCFs could reduce the complexity while keeping it flexible. But of course it depends on the WebResource and how complex it is.

  2. hi – this is am amazing resource as I don;’t find teh Microsoft documentation good for “how to” problems.

    I’ve posted to you on the PowerApps Community about an issue that I’m having and hope you can help./

    keep up the great work, it makes huge difference to people like me.

  3. We now have basic PCF working. What we were interested in doing was using the SharePoint Search API so that our users can search SharePoint without having to open a SharePoint browser window. I have been told that Dynamics 365 Search searches the Dataverse, but not SharePoint.

    So, a PCF that takes a search string and then displays the returned DataSet from SharePoint.

    1. I think there are a few ways to think about. Usually a PCF is only showing/editing the data. Of course is technically possible to make your own requests right inside the PCF, but usually you have to think about protecting data / user rights and psswords, and it’s better to have a backend component too.

      You can also have a Virtual Table for the SharePoint data. Actually the following announcement is telling us that we now get Virtual Tables for SharePoint out-of-the-box: https://powerapps.microsoft.com/en-us/blog/bring-microsoft-365-collaboration-to-your-model-driven-apps/

      1. Virtual Tables look interesting, but are read-only. I was thinking of wrapping the SharePoint API in a Custom Connector to allow for full CRUD and Search. This would make the UX clean. That said, the standard D365 Document Grid must be calling an API as the documents aren’t in the data verse, only the locations are.

  4. Hi Diana,
    I am following your example, for Single Line of Text, it is working fine. But for Multiple Line of Text, it is not working at all. Do you mind if I get some paid help from you. Please, ping me as soon as possible

      1. CellRendererOverrides.tsx

        for [Text] is working fine, but I am trying to override [Multiple] and the Grid does not respond with any changes at all.

  5. Hi Diana. Very Impressive Work

    One of our JavaScript web resources are outdated and no longer supported. We are interested in deploying PCF for the first time and need some guidance. Very similar to what you were able to accomplish with the whole number & choice fields, however our main requirement is based an condition. The condition statement is supposed to evaluate the whole number field against a range and highlight the choice field accordingly. There are multiple conditions actually and I can share the outdated JavaScript file for more details.

    looking forward to hearing from you!

    Arslan A.

    1. Hi Arslan,
      I guess this is about the Power Apps Grid customizer control.
      It depends on your use case. One way would be to calculate the optionset (choice) using form-scripting or Dataverse formula column. Then you would have the data availabe everywhere, and the Grid would show the color without a PCF.
      If you want to show that colors only on the Grid, than would be similar with this example from the SDK samples: https://learn.microsoft.com/en-us/power-apps/developer/component-framework/sample-controls/customized-editable-grid-control?WT.mc_id=BA-MVP-5004107#code, where the color for a money field is calculated based on a condition. You can also color the choice field based on the number field if you want to. That would work similar with the calculated column example: https://dianabirkelbach.wordpress.com/2022/09/19/implement-calculated-columns-with-power-apps-grid-control/ (the GitHub repository with the example is linked there)
      Hope this helps!

      1. Thank You for sharing your ideas. So the Calculated column method is very interesting but unfortunately it is not available in our region (US Eastern & Central). Same applies for form scripting, it is not supported for our environment. For the PowerApps Control, the one you shared applies to the editable grid so I am not sure if that will also work on the PowerApps read only grid? The SDK Sample you shared is close to what we are looking for except that the condition will be based on multiple numerical ranges. For example. function OE_RF(rowData, userLCID) {
        var str = JSON.parse(rowData);
        var createdOn = str.createdon.Value;
        var coldata = str.new_customerservicetime_Value;
        var imgName = “”;
        var tooltip = “”;

        imgName = “”;
        if(coldata >300) {
        imgName = “rbc_dot_red”; }
        if(coldata >240 && coldata <= 300) {
        imgName = "rbc_dot_yellow"; }
        if(coldata <= 240) {
        imgName = "rbc_dot_green"; }
        if(!coldata) {
        imgName = "rbc_dot_red"; }

        var resultarray = [imgName, tooltip];
        return resultarray;


      2. Let me share the links to what I mean:
        – the Dataverse formula column announcement was made in july 2022, so it should be everywhere. But it’s true that it’s a preview, so shouldn’t be used in production: https://powerapps.microsoft.com/en-us/blog/boost-maker-productivity-inside-dataverse-using-formula-columns/
        – by “form scripting” I mean this one: https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/attributes/setvalue?WT.mc_id=BA-MVP-5004107. It’s available in all moder-driven apps.
        – The Power Apps Grid which host controls is not the Read Only Grid, and not the Editable Grid. It’s the “(Preview) Power Apps Grid control”.It’s a preview which will eventually replace all the grid controls in the future: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/the-power-apps-grid-control?WT.mc_id=BA-MVP-5004107

        But you are right, except form scripting, the rest are still preview features.
        Right now you could use the form-scripting to calculate the optionset values, and based on the color assigned to the option you could use my ColorfulOptionsetGrid PCF: https://pcf.gallery/colorful-optionset-grid/

      3. Hmm…I know PCF is the best solution for our business need but Form Scripting and PCF development are out of the scope of my capabilities. Not sure if you would be open to coming on board for this project but I would like to setup some time and discuss the possibility if you would willing. I think our requirements are simple and easy for an experienced PCF developer. Please email me if you would be interested in such a opportunity and I can share more information accordingly. Please let me know if you cannot access my email for any reason. Regards

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Website Powered by WordPress.com.

Up ↑

%d bloggers like this: