Forum Discussion

LiranRom's avatar
LiranRom
Helper I
3 years ago

custom connector with documentation function is not work on service

Hi,

We have published our Power BI custom connector Desktop on Market Place.

We wish to add 2 parameters, so it will be more flexible on the desktop establishing connection phase.

 

We follow this https://learn.microsoft.com/en-us/power-query/handling-documentation

 

the connector working great on desktop. but not on service.

 

on service we got this error

 

Here are the relevant part of our connector ( I marked only the connector name )

 

 

We Add "DataSource.Path = false" to parameters, as we wish the data source that the customer will see will be the name of our connector follow this guide: https://learn.microsoft.com/en-us/power-query/handling-resource-path

 

What are we missing, why this is not working on Service?

 

Thanks

 

 

 

 

 

 

 

 

Need Help

5 Replies

  • LiranRom's avatar
    LiranRom
    Helper I
    3 years ago

    Hi lbendlin 
    In my connector I try to perform 2 things that lead to same error on Servic: Incremental Refresh and adding Documentation Function.
    both works on desktop, but when I publish to Service Power BI - they lead to same error.

     

    In https://community.fabric.microsoft.com/t5/Developer/problem-with-the-Incremental-refresh-with-the-Power-BI/m-p/3318777#M43379 - I tried to add Incremental Refresh, 
    In this post you can see more details - and here I only added the Documentation Function, and removes the Incremental Refresh parts - so no RangeStart / RangeEnd parameter, but only 2 parameters I needed.

    I did make the changes with the Web.Contents call - using relativePath and Query, but same result. same error on Service side.

    What am I missing?

    • lbendlin's avatar
      lbendlin
      Super User
      3 years ago

      Don't try to do too many things at once.  Troubleshooting is easier if you add features one by one.  I would think that the documentation option is the lesser issue. Try that first.

       

      For the other part - I don't think you should bake incremental refresh into the logic of the custom connector.  In my opinion a custom connector based on Web.Contents should only focus on the authentication process, not on the actual query.

      • LiranRom's avatar
        LiranRom
        Helper I
        3 years ago

        Hi, 
        I've divided and didn't do them on same time,
        after I didn't succedded with the incremental refresh I try to perform the adding documentaion function - but didn't manage to perform this also.

        can you help understand why the documentaion function 2 parameters not working in service?

         

        as for the incremental refresh - I don't get it - we wish to pass the RangeStart into the connector logic and we wish to use it as a range time filter. for example - after getting all my data, I wish the connector go fetch only last day updated data. is it not possible?