Dataverse Connector all activity tables are showing errors on regardingobjectidname

[Anonymous]

Hi,

I've tried refreshing a report and came across this error on the activitypointer table in Dataverse

I've tried other activity tables: email, task etc. but none of them will load because of this error.  So, I can't even write a new query or try to exclude the field(s) that it says are causing the issue

Not sure if something has happened to this connector?

[Anonymous]

Hi @Anonymous ,

Regardingobjectidname is a field that is used in the activity tables of the Dataverse Connector in Power BI. If you are seeing errors related to this field, it could be due to a few reasons. One possible reason is that the field is not present in the table that you are trying to access. Another possible reason is that the field is present in the table, but it is not being recognized by the Dataverse Connector. To troubleshoot this issue, you can try the following steps:

Check if the field is present in the table that you are trying to access. You can do this by opening the table in Dataverse and checking the field list.

Check if the field is recognized by the Dataverse Connector. You can do this by checking the field list in the Power Query Editor.

If the field is not recognized by the Dataverse Connector, you can try renaming the field in Dataverse and refreshing the data in Power BI.

If the issue persists, you can try using the OData feed instead of the Dataverse Connector to access the data.

Best Regards,
Community Support Team _ Caitlyn

[Anonymous]

Hi,

So I can't even get a list of fields in power query to check if it's present?  There are two steps in my query, source and then navigation.  It's fails at navigation because it's saying the field isn't present

 So I can't even load the table from Dataverse.

The field is present in metadata.  This is a crucial field for dynamics activities where you set the regarding.  It has an ID and a name.  I don't understand how it can't be there.