Product Dimension activation Check in D365 FO x++

     public boolean isProductDimensionActive(RecId _productRecId, RecId _EcoResProductDimensionAttributeRecId)

    {

    

        EcoResProductDimensionGroupProduct ecoResProductDimensionGroupProduct = EcoResProductDimensionGroupProduct::findByProduct(_productRecID);

        EcoResProductDimensionAttribute ecoResProductDimensionAttribute = EcoResProductDimensionAttribute::find(_EcoResProductDimensionAttributeRecId);

        FieldId dimFieldId = ecoResProductDimensionAttribute.getInventDimFieldId();


        return EcoResProductDimGroupSetup::newDimensionGroup(ecoResProductDimensionGroupProduct.ProductDimensionGroup).getFieldSetup(dimFieldId).isActive();


    }


// calling the above method 

select * from EcoResProductDimensionAttribute where EcoResProductDimensionAttribute.DimensionTableId == tableNum(EcoResFlavor);


   if(this.isProductDimensionActive(InventTableCopyFromLocal.Product,EcoResProductDimensionAttribute.RecId))

   {


// custom logic

}

Comments

Post a Comment

Popular posts from this blog

step 20 Update script for service model: AOSService on machine: CR-VM-Test-1

  Hi, Cause: This can be either happening because of timeout or files being temporarily blocked. A general approach to resolve this issue would be the following: 1. Restart the Environment and try deploying the package again. 2. If that doesn't work, restart the Services and try deploying the package again.  3. If that doesn't work and if you see the below-mentioned error in the Log file: The process cannot access the file 'K:\AosService\WebRoot\bin\Microsoft.Dynamics.ApplicationPlatform.XppServices.Instrumentation.dll' because it is being used by another process,  following the below mentioned Action Plan should resolve the issue. Action Plan: 1. Open a PowerShell prompt as Administrator 2. Navigate to <Services drive>\DeployablePackages\<Runbook ID>\AOSService\Scripts 3. Create a temporary directory for log files 4. Execute: .\AutoUpdateAOSService.ps1 -LogDir <Log directory from step 3>. (Will likely take 75-100 minutes to complete) 5. Once the manua...
Read more

How to Bypass Next in COC in D365 X++

 To Skip the next call use try catch    protected void addPurchaseLines(int _line) { try { throw Exception::Error; next addPurchaseLines(_line); } catch(Exception::Error) {          // write your logic here      } } if want to skip the code between ttsbegin/ ttscommit than use throw Exception::UpdateConflict; instead of throw Exception::Error; protected void addPurchaseLines(int _line) { try { throw Exception::UpdateConflict; next addPurchaseLines(_line); } catch(E xception::UpdateConflict; ) {         // write your logic here     } } Regards  Muhammad Farraz email: farazjaved01@gmail.com
Read more