Forum Discussion

bhanu431's avatar
bhanu431
Frequent Visitor
9 years ago

circular dependency detected

I have a report in which i have created a dependency for mainting the order. Let's Assume

I have Input data of table BSE Index with column Name Capital Markets in order

                                        BSC Bankex

                                        BSC Auto

                                        BSC Capital goods

The required order is BSC Auto

                                 BSC Bankex

                                 BSC Capital goods

To get data in this order I created a new table as (BSE Index order) and maintained relationship on it.

Pass three Months every refresh is going fine. But, from the morning i was getting an error message on App only

The refresh happining properly on PowerBI Desktop but the refresh happening failing on powerBI (app/site).

---------Error Message------------------------

 Last refresh failed: Mon Oct 24 2016 13:27:33 GMT+0530 (India Standard Time)
There was an error when processing the data in the dataset.
Hide details

Processing error:A circular dependency was detected: BSEIndex[Capital Markets], BSEIndex[Order], c33eabb6-47dc-49ea-aac9-1a6a1c460dc4, BSEIndex[Capital Markets].
Cluster URI:WABI-WEST-US-redirect.analysis.windows.net
Activity ID:691c69e9-c035-3195-8444-77f7972f7715
Request ID:55f6cc95-7aee-2f67-304a-31b09885a2cd
Time:

2016-10-24 07:57:33Z

 

 

8 Replies

  • MattAllington's avatar
    MattAllington
    Community Champion

    You seem to have a 1 to 1 relationship plus no other relationships. Is it possible that one of your tables now contains duplicate values?  Try deleting the relationship, then refresh, rejoin the tables and see what happens. 

    • bhanu431's avatar
      bhanu431
      Frequent Visitor

      Thanks Matt

       

      I have deleted the relationships and configured again, still the issue remains. Any other suggestion please

      • MattAllington's avatar
        MattAllington
        Community Champion

        Sorry to be pedantic. Do you delete, refresh all queries then recreate the relationships?  Or did you delete, recreate and then refresh. You should do the former. 

  • ankitpatira's avatar
    ankitpatira
    Community Champion

    bhanu431 Try chaning cross-filter direction of the active relationships from 'Both' to 'Single' and that should make this error disappear.

    • bhanu431's avatar
      bhanu431
      Frequent Visitor

      Thanks Antik,

       

      I tried this as well, it is not accepting single relationship between th tables. Any other Suggestion?