Forum Discussion

DebbieE's avatar
DebbieE
Icon for Community Champion rankCommunity Champion
3 years ago

Deployment Pipeline Rule Property no longer exists

We have Dev test and Prod

each has a dataflow connected to a database (Dev test and Prod

we set up rules for each

 

now when we are attempting to push the dataflow into Test we get the following

we have tried removing and readding the rule but cant seem to get any further. we dont understand why this is happening (The Learn more hasnt been helpful) 

 

can anyone give us any advice on what to do about this so we can get our code changes into test?

8 Replies

  • We had this problem and it turned out to be the naming of one of the tables in the samantic Model had a trailing space in it. Removing the space allowed to rule between DEV and PROD to be implimented. Just be aware that your report visuals may need fixing as they will have lost the path to correct table.

  • Hi - did you ever get a resolution to this, I'm hitting the same problem...

    • DebbieE's avatar
      DebbieE
      Icon for Community Champion rankCommunity Champion

      No we never did get this sorted. I lef this with another team to look at eventually. Whether they ever did raise a support ticket Im not sure. 

      • cbugs's avatar
        cbugs
        New Member

        I left this with a dev team on my side, it did look like someone had managed to get a hardcoded reference into the pbix that pointed at one of the data sources, and so the rule based pipeline was failing as it couldn't change everything. Dev team went in and did some data source management and I think it seemed to sort out the problem.

  • I seemed to have the same issue and fixed it through an alternative solution by using a parameter to define what the data source credentials are going to be e.g. create a parameter in the PBIX file (Semantic model) for DatabaseName & SQLServerName - See below: (Parameter Hardcoded in deployment rule to what you require it to be)

     

     

    I no longer for this error - this allowed me to refresh the semantic model thereafter.

     

    ##This may have be an issue where if you have parameters setup and want to add a rule to the data source - and could be conflicting, however I did not get a chance to test a PBI file without parameters..

  • Arti123's avatar
    Arti123
    Frequent Visitor

    Hi, did anyone find a solution to this as I am experiencing the same issue now. I deleted the rules and recreated them but still not working.

  • Just re-assign the workspace and it will be fixed.

    In my case I have Test => UAT => Prod

    The rules as well as the comparison of the Test and UAT environments were lost and I could not see either any rules that I have already assigned. Also it was recognizing all the items (semantic models & reports) as new and not existing in UAT.

    I Re-assinged the Test workspace and everything came back to normal!