• CIF telemetry enhancement for throwing meaningful error details rather than empty object.

    End user does not see any error on UI whenever any CIF method like retrieveRecord fails to fulfil. See an empty object("{"value”:{}}”). in error object. This inhibits ability to fix it.

    function (error) {

    console.log(error);

    Reference - retrieveRecord (JavaScript API Reference) for Dynamics 365 Channel Integration Framework 1.0 | Microsoft Learn

    // retrieve contact record

    var id = "b44d31ac-5fd1-e811-8158-000d3af97055";

    var entityLogicalName = "contact";

    Microsoft.CIFramework.retrieveRecord(entityLogicalName, id, "?$select=fullname,telephone1").then(

      function success(result) {

       res=JSON.parse(result);

        console.log(`Retrieved values: Full Name: ${res.fullname}, Telephone Number: ${res.telephone1}`);

        // perform operations on record retrieval

      },

      function (error) {

        console.log(error.message);

        // handle error conditions

      }

    );

  • Make Recent Items api/data/v9.0/UpdateRecentItems API configurable

    Issue - Customer would like to customize Recent records navigation which comes OOB for all model driven apps. At the moment their is no way to customize it.

    Ask - Make this navigation configurable, help reflect desired records.

  • addCustomView function isn't working/being recognized for power apps grid

    Issue - Customer is firing our addCustomView function https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/controls/addcustomview on Power Apps grid control - Power Apps | Microsoft Learn which is in preview feature. It is failing to recognize this function however same code does work for regular grids. We don't see this issue listed in known issues/limitations hence reporting it. Current implementation retrieves the lookup query using the fetch below, but Power Apps Grid does not work. The issue is that on Power App Grid (Event OnRecordEvent), the lookup column is not being set up based on the fetch. 



  • Rich Messages form for AMB aren't getting transported/migrated via Configuration Migration manager tool

    Customer configured Rich Messages form for AMB & would like to migrate them from one org to another. For this they used Configuration Migration Manager tool, Rich messages form does not get migrated(no error) however values does. Hence they have to create this form manually in the target org.

    There are many other Omni Channel configurations that break or don't get migrated hence need of an hour is to have some specific tool to migrate OC related config as this generic CMM tool isn't completely capable.

    Manage rich messages | Microsoft Learn

    Configuration Migration tool - Power Platform | Microsoft Learn

  • Synchronization Page in FSM does not provide details about Data to Upload

    Issue: FSM sync section Data to Upload only displays total number of rows to be uploaded, there is no breakdown based on table to provide the ability to understand the structure of outbound data.


    Question: How can we determine to which table/entity does the data to be uploaded belong to? Being able to see details about rows to be uploaded would still be a useful capability to support fix of future issues.

  • Provide view level filtering for custom PCF control on View level

    Customer requirement - We are setting the PCF Grid in the Entity View which doesn’t have much property to make the modification. We need this Grid to be displayed only in certain views ( Active projects). We need the 'Filter By' option in the column header for the PCF Grid developed with same as OOB Filter Option. 


    Currently, there is this enable filtering property that determines if filtering options are available to users in the grid column header dropdowns, it is ONLY available at Entity level.

    https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/the-power-apps-grid-control#configure-the-power-apps-grid-control 

  • Custom button are not showing up on DataVerse search Quick actions & Grid

    Issue -

    Quick actions buttons have been configured per these articles https://learn.microsoft.com/en-us/power-apps/user/relevance-search#quick-actions 

    For more information on how to configure quick actions, see https://learn.microsoft.com/en-us/power-platform/admin/configure-relevance-search-organization#configure-quick-actions-that-appear-with-dataverse-search-in-model-driven-apps  


    OOB buttons show up fine both on search quick action & grid however custom button(any) are not showing up neither on Data Verse search quick action nor on grid. We have validated that this custom button shows up on home grid. 


    Exact Repro Steps: On Data verse search, search for any account record, it will render matching records that will have quick actions associated on quick action menu & grid. 

    We have tried with all 3 enable rules however they don't work for custom buttons -

    ShowOnQuickAction 

    ShowOnGridAndQuickAction 

    ShowOnGrid 


    We followed steps documented in our article https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/command-designer-overview#command-bar-locations it seems that quick action buttons can be added or edited using new command designer however no luck(we don't see custom buttons showing up in quick action/search grid). We tried changing the order of the custom button , existing buttons were having 40,50 & 61 sequence numbers and we gave 45 for new custom button. Still we were not able to see the custom button.


    Tools Used - Ribbon Workbench & new command designer.


    References - Customize the command bar - Power Apps | Microsoft Learn

     

    Ask - Can we have these ability to add custom quick actions button on DV search/in future versions/releases, this will enhance search experience for customer end users.

  • Store phone call recipient information in phone call entity table along/instead of activityparty base table.

    Issue -

    When reporting from the phone call exported data the to and from fields contain the same guid as the phone call itself instead of the guids of the chosen lookup records.


    Ask -

    Yes we ultimately did use activity pointers as a workaround but it is extremely slow and taxing sql operation. Is there any reason the To and From fields on the phone call entity are designed this way? In future we should think about storing phone call recipient information in phone call entity table along/instead of activityparty base table. 

  • Restrict maintenance window further that shall avoid customer solution updates.

    Customer Reported Concern

    We frequently run in to issues while deploying our custom solutions because Microsoft updates are going on in either the source or target environments. We need to be able to set a maintenance window for all environment not just production and we also need to be able to restrict the days or be altered as to the planned day updates are going to happen. Having a window 7 days a week that Microsoft can use doesn't allow us to plan deliveries without conflict. We have had several Production deployments in a row that were delayed because of updates happening by Microsoft. Given these are our environment we should have a say in the update windows. Microsoft should not only plan the updates but notify us of the planned date so we can communicate if we need them to move it out, primarily for Production deployments.



  • Ability to deploy custom connector action changes in single solution

    Customer Scenario: We are deploying custom connector action via a Solution. When deployed manually as managed solution, actions are reflected in the target environment Dynamics_CFT_Test. When we used GIT pipeline with force overwrite = true, it didn't reflect. We found the deployment was done successfully from Solution history. It upgraded to newer version and uninstalled older one. Any upgrade/ update/ Import was not failed irrespective of GIT/Manual. We have the evidence that there is no failure during the deployment.



    Specifics: We have created a small solution containing only custom connectors and was deployed via git in target org. That time it reflected expected actions. Next time, when we deployed actual solution keeping custom connector actions it got overwritten to prior state (expected custom actions are not reflected). Then we again deployed that small solution via git with a newer version to the target org and it worked.

     

    Concern: If we have to perform the same each time whenever we deploy actual solution, will be a big task. Kindly suggest any better way.