Pavan Kumar Deepala CONSULTANT BA

Pavan Kumar Deepala

Joined: 11/8/2015

  • Calculated field to support for Lookup fields

    Thu, 17 Jun 2021 12:19:45 GMT – Dynamics 365 Sales – Needs Votes 

    Currently Calculated field does not support Lookup fields on either same entity or related entity. i.e for eg: A calculated field (on case) with condition : Account.primarycontact contains data set Value : incident.emailcontact equals Account.primarycontact If this is implemented a lot of unnecessary coding/workflows can be avoided for developers.

  • Business Rules have inherent activation order results in unexpected results #2107090010001109

    Thu, 02 Sep 2021 11:56:05 GMT – Dynamics 365 Sales – New 

    Business rules after deployment are not working as expected because we were informed that business rules have some inherent order and will work in that sequence only, because of that it is resulting in unintended results eg: consider 3 BR If Sales Revenue == 0 set Default Value 0 If Marketing Revenue == 0 set Default value 0 If Sales Revenue == 0 and Marketing Revenue == 0 , set Total Revenue mandatory else set Total Revenue not mandatory Consider the above example, the expected result is Total revenue is required if others are 0 and not if other wise, however after deployment it is always showing as non-mandatory. Business rules are supposed to be working on condition based and not order based. Hope this would be fixed soon.

  • Environment aware Environment variables are required

    Tue, 21 Sep 2021 03:49:16 GMT – Dynamics 365 Customer Voice – New 

    The reason we use Environment specific values is that application should automatically detect the current environment and take the appropriate values. If these are just configuration values which in general all developers use, I don't see any value addon I Suggest since multiple values are possible for a variable ; A Environment record (OrgName) should be created and against it the values should be created and once deployed the values should be read from destination orgname. This way it removes the overhead of verifying the values in each environment post deployment . for eg : Orgurl -> devorg: https://devorg.crm.dynamics.com sitorg : https://sitorg.crm.dynamics.com prodorg: https://prodorg.crm.dynamics.com Redirected ideas portal from https://github.com/MicrosoftDocs/powerapps-docs/issues/1276

  • Support for deployment with SPN for connection settings of power automates

    Wed, 16 Mar 2022 09:42:45 GMT – Power Platform Governance and Administration – New 

    Hi Team,


    In Deployment Automation with Azure DevOps the recommended way is Application user (Azure SPN) as mentioned at https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tools#connection-to-environments . However for connection settings automation mentioned at https://docs.microsoft.com/en-us/power-platform/alm/conn-ref-env-variables-build-tools#step-4-use-the-deployment-settings-file-for-build-tools-tasks we need a generic service connection to establish the same.


    Orgs have their own policies of MFA which is becoming increasingly difficult to automate and conform to MFA. Hence can there be a way to share the connections or a supported way to cover both of these.


    Thanks in advance

    Pavan

  • Automation surrounding Advance Find; ex: ability to Embed Advance Find on entity forms

    Tue, 19 Jul 2022 11:50:27 GMT – Dynamics 365 Sales – New 

    Hi Team,


    Though the Advance Find feature is there for quite a while, but no Automation features surround it.


    Use cases like

    • Ability to build custom queries by the user which can be leveraged in automation. We can use {CrmUrl}/SFA/goal/ParticipatingQueryCondition.aspx?entitytypecode={entitycode}&readonlymode=false but it is not supported as there is documentation surrounding it.
    • Ability to pass dynamically/custom query params to the advance find
    • Ability to request executed results from advance find programmatically
    • Ability to have a view selector allowable to be set on Forms, for automation to be run against


    Currently too much configuration is involved by developers to make it happen. If advance find as a tool is exposed for building around it, It would tremendously increase the use cases and drives towards faster adoption and Drives Lowcode development.

  • New Schedule Board Experience for Customer Service

    Tue, 28 Mar 2023 15:45:53 GMT – Dynamics 365 Customer Service – Needs Votes 

    The New Schedule board capability is present for only Field service (https://docs.microsoft.com/en-us/dynamics365/field-service/preview-schedule-board) and not yet available for the users of URS with Customer service experience. However the deprecations of calendar settings (Schedule engine = URS) was already part of URS upgrade. If implemented the appointment scheduling will add lots of value for Customer service users as well. Hope this will be considered . Cheers !!