Power Automate Function - This operation on table '' may not work if it has more than 1000 rows.

 During the creation of my first function to be used with Power Automate I received this warning when attempting to use the 'Filter()' function.  This was odd as I know this function IS delegable (The warning is saying it will become NON-delegable).  The warning ended up being correct as my flow failed because it was trying to filter against a table with more than 1000 rows.

With some trial and error I found two comparisons in my filter that were causing this to occur:

1. Comparing a Yes/No choice field to true/false
    

    myChoiceField = true

This will cause the filter to become non-delegable.  In this cause you need to get the actual Yes/No value from your field.  It needs to look like this:

    myChoiceField ='My Choice Field (My Table)'.Yes

2. Using a 'Grandparent' lookup field (A lookup field to a lookup field)

In my table I have lookup field to a Header/Parent table which then does a lookup field to another table.

    'Initial Lookup'.'Next Lookup'.GUIDField = GUID(GUIDValue)

To solve this it is easiest to create a GUID field on the table you are using in your 'Filter' with a formula:

    Text('Initial Lookup'.'NextLookup'.GUIDField)

This will give you the GUID in a text field on your table. You can then make the comparison and your 'Filter' stays

delegable!

D365 F&O Dual-Write Error: Couldn't resolve the guid for field: teamid.businessUnit

 After refreshing a Tier 2 from another Tier 2 and attempting Dual-Write, We received the following error:

Couldn't resolve the guid for the field: teamid.businessUnit. The lookup value was not found: [BusinessUnit Name]. Lookup parententity: teams, lookup result: .. Try this URL(s) to check if the reference data exists: https://operations-[envrionment].crm.dynamics.com/api/data/v9.0/teams?$select=name,teamid&$filter=… eq '[guid]'

Turns out the solution is very simple.  Go into Power Platform Admin Center, Select 'Manage', then select your environment.  On that page select 'Business Units'. Find you business unit, select it, and then hit 'Edit'.

Simply change the name by adding a single character at the end, save it, then remove the character you added.

That's it!

AX 2012 - Failed to find workflow

 We recently had an issue where our workflow batch job would fail with this error.  Other workflows would be partially run but not fully due to the failure.  For example, if you approved a workflow it would show the approval in the 'Workflow history' but it wouldn't advance the workflow.  It would just sit in review.

The solution turned out to be pretty easy. I found this blog post. 

Run this query to get a RecId of the corrupted record:

Select a.RECID 
FROM SYSWORKFLOWMESSAGETABLE a 
WHERE a.ROOTCORRELATIONID 
NOT IN(Select b.ROOTCORRELATIONID from SYSWORKFLOWTABLE b) 
and a.MESSAGELIFECYCLESTATE = 1

Run this query to update the record found:

Update SYSWORKFLOWMESSAGETABLE 
Set MESSAGELIFECYCLESTATE = 2 
where RECID = [RecId from above]

That's it!

D365 F&O - No Certificate Found for id

 Recently I created a new Tier 1 environment and refreshed the DB from another Tier 1 environment. After attempting to edit a Vendor, we received the following error:

Encryption error occured with exception: Microsoft.Dynamics.Ax.Xpp.Security.CryptoEncryptionException: Encryption error occured with exception: Microsoft.Dynamics.AX.Configuration.CertificateHandler.NoCertificateFoundException: No certificate found for id 'xxx'.

This is being caused by the previous environment's connection to dual-write.  Whereas my new Tier 1 doesn't have (nor need) dual-write, the solution to this is the following:

Using SSMS delete all records in the following tables:

DUALWRITEPROJECTFIELDCONFIGURATION
DUALWRITEPROJECTCONFIGURATION

This will prevent the the environment from attempting to use Dual-Write.

D365 F&O error opening project in VS 2022 - The imported project was not found

 I recently switched to a new Tier 1 machine and VS 2022 for my F&O development. After pulling down all items in version control I received the following error:

The imported project "C:\Program Files (x86)\MSBuild\Microsoft\Dynamics\AX\Microsoft.Dynamics.Framework.Tools.BuildTasks.targets" was not found.

The fix for this was relatively easy.  Open the project file in Notepad++ (Or another text editor) and change this line:

<Import Project="$(BuildTasksDirectory)\Microsoft.Dynamics.Framework.Tools.BuildTasks.targets" />

To this:

<Import Project="$(BuildTasksDirectory)\Microsoft.Dynamics.Framework.Tools.BuildTasks.17.0.targets" />

D365 F&O Tier 1 Update Failure Step 25 AOSService

When upgrading a tier 1 environment you could receive the following error:

GlobalUpdate script for service model: AOSService on machine

This usually means an issue with the DB sync, however, the log zip file doesn't always contain a file indicating the error.  Here are some steps to fix this issue:

1. Ensure VS 2022 is fully upgraded.
1. If you had to upgrade VS 2022, uninstall D365 F&O extension
2. Re-install extension from K:\DeployablePackages\                                    [ID]\DevToolsService\Scripts\Microsoft.Dynamics.Framework.Tools.Installer.17.0
2. Full compile of ALL modules
3. DB Sync
4. Restart environment
5. 'Resume' upgrade

D365 F&O Service Update failure DevToolsService

Recently when upgrading tier 1, cloud hosted, environments from 10.0.41 to 10.0.42,43, or 44 I received the following error:
 
Update script for service model: DevToolsService on machine

On some of my environments I would receive an error indicating it couldn't find VS 2022 and others that had VS 2022 it was another error.  

In order to get past this I would do the following:

1. If missing VS 2022, install it.
1. If it is already installed, update it.
2. Remove the D365 F&O extension if it is installed.
2. Install D365 F&O extension from K:\DeployablePackages\[ID]\DevToolsService\Scripts\Microsoft.Dynamics.Framework.Tools.Installer.17.0
3. In the same 'Scripts' folder, run the powershell command '.\AutoUpdateDevToolsService.ps1'
4. If that is successfull, copy and make a duplicate of that command.
5. Delete all code in the original .ps1 file and then resume your service update.