Missing table in Dataverse

[Anonymous]

Hello! 

I have been struggling for a couple of days with a specific table in Dataverse. I want to automate parts of the onboarding process and send a email to a new employee the day they start. We use the HR module in Dynamics 365 Finance & Operation. When a new employee is added, a table in D365 is updated.

I start a Power Automate flow with the Dataverse trigger "when a new row is added". According to the following link (Dataverse tables - Human Resources | Dynamics 365 | Microsoft Learn), the Table that I want to use for my trigger is called "Worker/cdm_worker" in Dynamics 365. The problem is that when I choose the table I want to use for my trigger, I cant find the "Worker" table.  

So, I know there could be many reasons for this but I suspect that it is an integration problem. But where do I start? What questions do I need to answer in order to get to the root of the problem?

Thank you very much in advance for any help or input!

[AaronKGumbs]

Hey!

Unfortunately this is by design. Dynamics 365 HR tables available via Dataverse are considered Virtual Tables, which won't show in the Dataverse connector. I am unclear on the solution for being able to use Dynamics 365 HR within Power Automate, but you may be able to achieve a workaround using other Dataverse features such as Business Rules. 

[Anonymous]

Hi! Thanks for you answer!  I want to make clear that we are using HR modules in D365 Finance & Operations and not the stand alone HR software.

So, I have managed to use a Business Event as a trigger and it actually works fine, the problem is that I cant get the data? For example, a new employee is added, the automation is triggered, but then what? I want to say "send mail to the adress in column X in table Y"

The flow below works fine: When a new employee is added, send an email to me. But I want to send the mail to the person that just got added... 

Next, I have seen other people use the "workers" table with dataverse connectors before, but maybe its more complicated than I first thought...

[AaronKGumbs · Accepted solution]

Gotcha! The Worker table in Dataverse is from Dynamics 365 Human Resources, so for you to use the Dataverse connector with data originating in Finance & Operations, you most likely need to check whether your org is using Dual Write and syncing data from source to target. If you're not using Dual Write between Finance & Operations and Dataverse, then you'd need to continue to use the Finance & Operations connector here. I would recommend that you try to use the 'Get a record' action from the same connector to identify your worker. This will (hopefully) allow you to obtain the email address of the person, which you can then use as dynamic data in your Send An Email action.

[Anonymous]

Wow! Thank you so much! I think I can make this work without the dataverse connection. I successfully got the "workers" table with the "List items in table", but when I add "get a record" I run in to problem. I see two possibilities: 1. My flow is not set up the correct way 2. I don't have the correct permissions to get the record. Have you seen this error code before? 

"NotFound
clientRequestId: ebfb2638-5ebc-329e-9se7-cf6b587e6451"

(note that numbers and/or letters have been changed for integrity)

Another related question: In what order are the tables sorted by default? I am thinking of which row I need to point towards to always get the last added employee. Is it the last or first row in the list?

[AaronKGumbs]

I'm really pleased to see that you're now able to see the table! Please forgive me here if I can't help you all the way as I'm straying into parts where I've not experienced this exact connector, but I'll do my best.

The error you're receiving is error 404 which is a commonly used error code for a server side issue. This is always not found, and therefore with the format of your GUID (which looks correct), it's complaining that it can't find the Worker with that GUID.

Now, before we try to solve that, I've noticed that you're manually triggering the flow and then getting all of the items before trying to find your record. This has added an 'Apply to Each', but we're trying to make sure that we send this email when a new worker is created which would be better than manually executing and searching all items. We have two options here:

1. Try to narrow down the items listed to one unique record based on a value you can actually get to, or,

2. Does this connector allow you to specify 'when a new record is created', where you can then select for it to trigger on the Worker table? If it does, this will allow you to take the correct GUID for the new Worker directly from the trigger for your Send Email step. 

Again, apologies if this doesn't quite work, I'm counting on my theoretical knowledge of Connectors and practice experience with Dataverse in the hope that they match up!

[Anonymous]

Hello again, 

After a week of trial and error I finally made this work. Big thank you to Aaron who pointed me in the right direction! 

For future reference, here is what worked for me:

The flow is scheduled to trigger every day at 07:00. The table/list "Employees" is then scanned to check if any value in the "EmployeeStarterDate" column contains todays date, if yes then send an email to that person. The expression I used to get todays date is: formatDateTime(utcNow(),'yyyy-MM-dd').

Once again, thanks and good luck with your flows!