Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I am trying to create a Microsoft FLOW to Dynamics NAV 2017 Cronus db and running into issues. Thought I’d run it by you.
Below are the steps I am following:
My Flows >> Create from Blank. Type NAV, it comes up with the 2 available options. Select Dynamics NAV - When a record is created
Then it prompts for Connection Info. I created a webservice entry in NAV 2017 for the Item List Page and copied and pasted the ODATA URL into this field from NAV. I tried entering the username a few different ways since it was failing. But the latest entry for user name and company name are exactly as in NAV 2017 Cronus db.
Then when I click Create, it comes up with the Table Name selection. When I click the drop down button, it shows the error: "Could not retrieve values. Invalid Mashup expression using supplied values. inner exception. Dynamics 365 for Financials Request failed. The remote name could not be resolved Mycomputername.domain
Hi, did you ever get any success with this, I have the identical problem
Try to use with NAVUserName or Web Service Access key.
"Web Service Access key" i think is mandatory for NAV 2017 to avoid Mashup error.
i ask to Microsoft about documentation\configuration for NAV 2017 (Microsoft Flow is in Preview).
let you know ASAP.
Thank you Roberto
good news, i asked two hours ago to my friend Suvidha to write a post about this issue.. she was wraiting a post about this topic..... just in time.....
please read this post... (is about Dynamics 365 but can be useful also for NAV 2017)
Created 2 flows.. 1 for Dynamics 365 and 1 for NAV2017
Dynamics365 flow is working and NAV2017 flow is not working.. need to investigate..
I read through the blog. It was helpful but the issue remains when trying to create a FLOW for Dynamics NAV 2017 - keep running into the MASHUP error -
Could not retrieve values. Invalid Mashup Expression using supplied values. inner exception: Dynamics 365 for Financials: Request failed: The remote name could not be resolved: 'vparameswaranlt.sg.com'
This error comes up when trying to select the table on the FLOW. All connection settings info. are entered accurately to my knowledge and as explained/illustrated in the blog.
This is standard Cronus NAV 2017 database. All client and server components are installed locally on my machine. The NAV2017 Web Client works correctly. Do we need to have SSL enabled on the NAV server for the FLOW to work?
Here are my settings:
ODATA Feed URL: vparameswaranlt.sg.com/.../OData
Username: SG\VPARAMESWARAN (exactly as in the User card in NAV)
Password: Web service key (copied from the User card in NAV)
Company: CRONUS USA, Inc.
Just replied to Roberto. I read through the blog he suggested. It was helpful but the issue remains when trying to create a FLOW for Dynamics NAV 2017 - keep running into the MASHUP error -
Does youR Web service access key have an equals sign at the end?
Yes, it does.
Did you ever manage to solve this? I've got the same issue. The error sounds to me as if when trying to connect to NAV 2017 it is expecting Dynamics365 instead? I have not tried an SSL connection yet, just http. Wonder if that could be the issue?
I found this thread while investigating this error for Dynamics 365 for Financials and figured I'd add what the solution was in our case. This issue was being caused by a specific Page\Web Service that had been exposed. Specifically page 9177 "Allowed Companies". Once we removed this published Web Service the Flow Connection started to work.
There may be other Web Services that break this functionality. I had to go through and remove\re-add them one by one to find the bad one.
Hi, I had the same issue. After some hours of investigation I found that Odata port was not open in my VM. After opening Odata port (7088 in your case) everething works like a charm.
Look at my blogpost on this topic
I'm trying to connect to flow with dynamics NAV 2017. I have a VM on Azure with the NAV.
When I try to connect to flow I have this error:
"Não foi possível obter os valores. Credentials are missing or not valid. inner exception: The credentials provided for the Dynamics 365 for Financials source are invalid."
I'm using the right URL (it works on browser), my user name, the web service access key and the company.
Anyone with the same problem?
Did you looked at my blog ?
I suppose you used user password instead of web service key
If you have not specified the Base Odata Url in NAV Administration, you will not be able to connect.
I passed the request to NAV support.
Flow is changed (like Power BI.... etc.)
There seems to be problems with updating MS FLow that natively uses OData4.0 instead of 3.0 previously used; In practice, the existing\udated connector on NAV 2018 connects native to 4.0 during the mashup (not NAV 2017).
"Just tried it with oData V4 URL and get the same result as with the normal oData URL.. errors on creating connection then same issue trying to create the FLOW itself. Interesting it works with 2018 though, wonder if an update is due to 2017 to make it work again."
Check "Company name": characters "/ * % or & ???" are not allowed in NAV 2017 > supported only since NAV 2018...
I'll let you know as soon as I get more information about this issue.
Business Applications communities