You are not having an option called Republish directly. You need to click on THREE dots, click Edit, make some changes in the QUERY then Click Next --> Check the Table too --> Click Next --> and PUBILSH it again.
Its like a kind of altering, if you dont have any issue, recreate and retrigger for a safer side.
Could you please tel me which field you are trying to update. Is it a lookup field?
Because in your screenshot am not seeing any field getting mapped
Please mark as Answer if it is helpful and provide Kudos
When I try to republish as you suggest I do this:
@rtmystic I'm having the exact same issue. The error I'm getting after the publish fails is useless. All it says is "Something went wrong" and in the details it gives a session and a request GUID.
Were you able to get around this? if so, what was your solution?
I submitted a ticket to Microsoft support. Hopefully I can find out what the issue is.
I discovered that my alternate keys weren't properly defined on the table I was importing. I had to redefine my alternate keys and redo the import. Then it worked. It's been a few weeks now. So I can't remember exactly the key that was missing. But here's the info that MSFT added to the ticket closure information. Hope it helps:
MSFT REPLY: I want to inform you that I shared your case with my technical team for review, and after a discussion, I want to share with you our outcomes:
Lookup columns create relationships between Dataverse tables, utilizing a specific GUID recognized only by Dataverse. You can find more information about lookup columns here: Create a relationship between tables by using a lookup column - Power Apps | Microsoft Docs
To map a Dataverse record (GUID) using lookup columns to an external system like PowerApps dataflows, the "Alternate Keys" must be defined as stated in the following Microsoft document: Define alternate keys to reference rows with Microsoft Dataverse - Power Apps | Microsoft Docs. It states:
"Alternate keys provide an efficient and accurate way of integrating data with external systems. It’s essential in cases when an external system doesn’t store the Globally Unique Identifier (GUID) IDs that uniquely identify rows in Microsoft Dataverse."
I also want to share other links to helpful information for this process:
- Define alternate keys using Power Apps - Power Apps | Microsoft Docs
- How to map a Lookup Column in a Power Platform Dataflow (apprising.co.nz)
The lack of alternate keys was the reason of these errors, but this information should address the process of creating a data flow using lookup columns for you in the future.
Keep up to date with current events and community announcements in the Power Apps community.
Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.
Check out the latest Community Blog from the community!