use more than 10 fields in a calculation chain

Comments

13 comments

  • Rainer Grabowski (FVM)

    Welcome to the "calculation to deep"-club! :(

    1
    Comment actions Permalink
  • Stefan Ukena

    Hi Jan & everyone who has the same problem,

    the way Podio determines which features to implement next is to consider how many people really need something. So, if you really want this, send an email to support or add your comment here.

    Rainer, of course you'll know this already. :)

    Best,
    Stefan

    1
    Comment actions Permalink
  • Rainer Grabowski (FVM)

    The former Podio Chief Developer, Christian Holm, has written in an answer to a help question some month ago:

    This happens if you have a very deep dependency tree for your calculation fields. If a calculation depends on a field that is also a calculation, which is also .... 10 times, then you get the given error message. This is not something that should really happen under any normal circumstances, so my guess would be that you have made the calculations much more complicated than they needed to be. Don't forget that you can do a very deep calculation in one calculation field, so you don't need to depend on other calculation fields too much.

    https://help.podio.com/hc/communities/public/questions/201348133--the-calculation-is-too-deep-?locale=en-us

    And indeed, sometimes it helps to rethink the structure of your calculations, but not in every use case. I'm afraid, Podio won't change this limitation of 10. But I think, one "workaround" could be, if Podio would make it possible in Advanced Workflows to pull data from calculation fields into number or text fields (cause Advanced Workflows can be triggered by changes in calculation fields). This would also help, to store calculation results (e.g.if you want to build a system of incrementing project numbers). And this in combination with the possibilty for Admins to define specific fields as "always hidden for user" , which is wished by many admins for a long time, would offer some very nice opportunities for calculation flows.

    Rainer

    1
    Comment actions Permalink
  • Jan Richter

    Hello Rainer, hello Stefan,

    If you manage especially the financial part of a business, the calculations can't be deep enough!

    I think the workaround with workflows could help. Thanks on this one.

    But shrinking the number of possible calculations is still a big problem the end. We don't want to combine app-data via connection fields. It's too much work in the daily business. And workflows are depending on changing data. That could cause other issues. But let's see how this works. Thanks a lot.

    Greets, Jan

    0
    Comment actions Permalink
  • Jan Richter

    I tested workflows. This feature is not that good. As long as you can't include calculations it's super useless. Will there be an update on that?

    0
    Comment actions Permalink
  • Rainer Grabowski (FVM)

    Hi Jan,

    ever tried the extension GlobiFlow or another solution via API? If you won't create your own API-solutions, Globiflow is a really great tool https://podio.com/extensions/2. GlobiFlow has it's own Podio workspace where you get help and information. Or ask Stefan (a Podio Preferred Partner) who has developed several solutions.

    Rainer

    1
    Comment actions Permalink
  • Jan Richter

    Hello Rainer, I've seen it before but never worked with it. I think I'll test it. Thank you.

    0
    Comment actions Permalink
  • Jan Richter

    Still depressing - still need that!

    0
    Comment actions Permalink
  • Paul Renshaw

    Crying with the same warning. I agree, if you are dealing with financials and you want to avoid (error-prone) manual entry in as many places as possible, 10 levels is not enough. Here's my example:

    Since it's been 3 years since the last comment, I would put money on that people have had this issue, seen no updates, and just stopped using Podio and gone with dedicated software. Podio is great for prototyping apps, but you will almost always get to a point where dedicated software is necessary.

    0
    Comment actions Permalink
  • Rainer Grabowski

    Hi Paul,

    it's rather easy to break up the chain if you use Globiflow. That way I concatenate 40+ calculation fields across apps and workspaces.

    Rainer

    1
    Comment actions Permalink
  • Jan Richter

    Rainer is right. I meanwhile use Globi Flow myself after he recommended it to me three years ago and now our entire business is fully automated with endless calculation chains. Read my first question - everything solved.

    In plus: calculation fields are just shit. U can never rely on the actual data - laggy, unreliable, buggy... just never use them.

    0
    Comment actions Permalink
  • Richard Hedger (Parc-des-Crêts)

    Rainer Grabowski

     

    Hi Rainer, how exactly are you breaking up the "too deep" chain with Globiflow? Can you just state the basic approach. Thanks

    0
    Comment actions Permalink
  • Rainer Grabowski

    Hi Richard, 

    that really depends on your chain. In one place (app) where it is possible you add a number field/text field  instead of the calculation field. Let's call this app App 6 (cause it's the 6th link in the chain): 

    In App 5 add a hidden category field, call it e.g. Action, with one category "go". 
    Then a Podio flow in App 5: When the calculation field "Link 5" is updated, update item in field Action to "go". 
    Then a Globiflow in App 5: When field "Action" is updated and field Action == "go", 
    Get ref. from App 6
    continue to App 5
    Now you have to do a calculation in GF which returns the same result as your calculation in Podio. Then update the  number field/text field in App 6. 
    In App 7 modify your code so that it references the number field/text field in App 6 instead of the calculation field in App 6. 

    Rainer
     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk