Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Can't setup Incremental Refresh for Dataflow to SnowFlake

I get an error when I try to setup incremental refresh to a Snowflake view in a Power BI Dataflow. 

 

Error Message: Model is invalid because it contains duplicate query names. Error: This document contains a duplicate member 'RangeStart'.

 

When I try to setup the incremental refresh, I am seeing duplicates for every datetime column in the dropdown, but this isn't in the actual data. I wonder if Power BI Service is finding the names in the view and in the table referenced by the view.

 

 

8 Replies

  • This looks more like a duplicate parameter.  Did you define two RangeStart parameters/queries in Power Query?

     

     

  • V-lianl-msft's avatar
    V-lianl-msft
    Icon for Community Support rankCommunity Support

    Hi Anonymous ,

     

    The Table you are drawing a reference to has duplicate values. 

    Please try to fix the issue in Relationships by changing the Cardinality to 'Many to One'.

     

    Best Regards,
    Liang
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Unlike pbix data model, you do not need to define RangeStart/RangeEnd parameters in a dataflow to setup incremental refresh. You just need a date column in datetime format. 

     

    In your case, you should just delete the rangestart parameter from your Dataflow. 

     

    Please mark this as resolved if this helps. 

     

     

    • lbendlin's avatar
      lbendlin
      Icon for Super User rankSuper User

      Let me rephrase that.  

      Unlike a Power BI dataset (where you need to define the RangeStart and RangeEnd parameters in Power Query on the desktop) for dataflows the Power BI service creates these parameters for you when you indicate that you want incremental refresh (and specify the datetime column for it).  Power BI service will also automatically add the filter step to the end of the dataflow M code (which is stupid, in my opinion - it should be possible to specify that filter much earlier in the code).

       

      If you had manually created the parameters and then try to enable incremental refresh for a data flow all hell will break loose. Most of the time you will lose access to the dataflow and will have to delete and redo it.

      • juanserm's avatar
        juanserm
        Frequent Visitor

        I understand the response you are giving (makes total sense), but what I can't figure out is how do I go about limiting the table size for design purposes if I can't add any parameters? When working with datasets that's not a problem because RangeStart and RangEnd are override by the incremental refresh ones, but in this case I have no other choice but load all the data every time I need to work on the dataflow design? (BTW, in my case I'm working on a Datamart, but it behaves pretty much like a dataflow in this sense).