How can we improve TrackVia? What features should come next?

Using {{OLD}} Through Parent/Child Calculations

Having tons of potential customers who need historical data on orders. Orders link to a Products table with pricing. The problem is that the pricing on products can change over time, and changing on the Products table changes all historical pricing data for that product.

Love that {{OLD}} is in place now, but doesn't work for this because it needs to reference a calculated field.

2 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        Hey Alex, any word on this? This is popping up in a few current/upcoming projects.

        No worries if not, you guys seem to be working on a lot of stuff. Have been enjoying the new features :)

      • Alex commented  ·   ·  Flag as inappropriate

        Hi Markwood,

        Thank you for the feedback as this is an understandable issue. When parent values are updated, those cascade to all of the children. Additionally, we have limited triggered fields' ability to reference parent fields for performance reasons.

        While there currently is not an easy, scalable solution for this at the moment, we are working on a new logic feature that will accomplish this without required more calculated fields being added to the table. We'll keep this post updated when it is available in the near future!

        Regards,

        Alex

      Feedback and Knowledge Base