Forum Discussion

Mornagli's avatar
Mornagli
Icon for Helper III rankHelper III
5 years ago
Solved

If I add custom column in Power Query that depend on specific column - each row the API get request?

I fetch my data with MPBI from Odata feed with an API call, the data is approximately 50,000 rows. After i get tha data, when im in Power Query - I try to add new custom column that relies on ex...
Need Help
  • lbendlin's avatar
    lbendlin
    5 years ago

    yes, and yes.

lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
5 years ago

Since this is an ODATA feed  - have you considered using ODATA filtering for your request?

Mornagli's avatar
Mornagli
Icon for Helper III rankHelper III
5 years ago

Hi lbendlin ,

 

I need couple of tables from this source, so i put the url that give me all the tables, And from it i take the tables i want.

If i will fetch each table separately, it will make diffrence?

 

With the filtering i will use for create 'Incremental refresh', but i need to understand why changes that i make in the Power Query after i have the table make problems when i try to 'Close&Apply'... And if there is an option to add columns and make changes in the Power Query' without call again to the API server for each cell.

  • lbendlin's avatar
    lbendlin
    Icon for Super User rankSuper User
    5 years ago

    if you already know which tables and columns you need then you can avoid a lot of work.  If however you don't have that prior knowledge then you have to use the long winded process.

    • Mornagli's avatar
      Mornagli
      Icon for Helper III rankHelper III
      5 years ago

      Thank you for your replays lbendlin .

      I know which tables i need, but maybe in the future i will need more.
      More importent for me is to know if after i choose specific table and load it to the Power Query, the changes that i want to do can be only loccally and not to active tha API GET request for each change. 

      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User
        5 years ago

        That's a decision you have to make for yourself - depending on size and source performance . Try one way and if it's not satisfactory then go the other route.

         

        Also:  You need to distinguish between the effect this has on you as the developer/dataset refresher and the effect it has on your report consumers.  If you have to wait longer but they have a good experience then I would call that acceptable, definitely better than the other way round.