Forum Discussion

Julian23K's avatar
Julian23K
Regular Visitor
3 years ago
Solved

oData Query To Dynamics 365 Does Not Fold

Hi!   I want to generate a table in Excel with Power Query. For this I need to map external (vendor) article numbers to our internal article numbers. I request the latter from our Dynamics 365 inst...
Need Help
  • Julian23K's avatar
    Julian23K
    3 years ago

    Ok, this actually works and it's significantly faster. URL-length doesn't seem to be a problem.

     

    OData.Feed("https://xxx.operations.dynamics.com/data/VendorProductDescriptionsV2?$select=ExternalItemId,ItemNumber&$filter=ExternalItemId eq '" & Text.Combine(#"externalIDlist", "' or ExternalItemId eq '") & "'", null, [Implementation="2.0"])

     

    It's still quite slow though.

    Why are these "professional" Microsoft products such a mess. ğŸ™ƒ

     

    Thanks for the input!

ImkeF's avatar
ImkeF
Community Champion
3 years ago

Hi Julian23K ,
buffering will stop the folding.
Also, ignore what Power Query indicates about folding, as that might be wrong. 
Your statement until #"Filter Rows" should fold, provided you don't buffer it.
Just check with monitoring the web traffic.

  • Julian23K's avatar
    Julian23K
    Regular Visitor
    3 years ago

    Thanks for the quick response.

     

    buffering will stop the folding.

    I know, I only buffer after the filtering, once I got all my data from that feed, so the query is not triggered multiple times during further processing.

     

    Also, ignore what Power Query indicates about folding, as that might be wrong. 

    That it good to know, lol.

     

    Just check with monitoring the web traffic.

    Will do. Maybe it's just slow, because our Dynamics instance is a mess. ğŸ™ƒ

    This simple example query above takes forever.

    • Shahfaisal's avatar
      Shahfaisal
      Solution Sage
      3 years ago

      I don't believe D365 using OData supports much query folding, if any. OData is inherently slow and I strongly recommend that you use a different approach. OData is not reliable unless your data volume is really low (less than 20,000 rows in each table)

      Assuming you are using D365 F&SC (aka D365 F&O), I advise you to use Export to Azure Data Lake

      • Julian23K's avatar
        Julian23K
        Regular Visitor
        3 years ago

        The query result is not very large, like not even 100 tables per query. The table I query from however is very large. So if I just write my own oData query (never done that before), I should be good, right?

         

        Like this?

         

        OData.Feed("https://xxx.operations.dynamics.com/data/VendorProductDescriptionsV2", null, [Implementation="2.0", Query="$select=ExternalItemId,ItemNumber&$filter=ExternalItemId in ('F000_68465165848', 'F000_68465165849', 'F000_68465165850')"])