Skip to main content
Solved

Tracking Most Recent Data

  • February 27, 2026
  • 0 replies
  • 84 views
Forum|alt.badge.img+5

Good day everyone!

 

This is likely convoluted. I haven't been able to figure a way to actually do this and I feel like I'm missing something obvious.

 

I have a couple of tables that will hold some information.

The tables involved:

 

Asset Table

Affected Asset

Ticket Asset

 

The asset table hosts the information of the Asset itself (Serial Number etc). We create a new record in the Affected Asset table based off the information in the Asset table that attaches ticket information to it.

 

I'm trying to add information to the affected Asset Table that when we create that record, it will record what's wrong with that asset and why we are getting it back.

What I want to do is. 

 

When we go to add the Asset onto an OOW Ticket, that it populates the Ticket Asset Report with the Latest "laptop Issue" field based off the Assets Serial Number (unique identifier). 

 

I am unsure how to grab the most up to date. I likely skipped a step by cutting out the Asset Table in general?

 

I made the Affected Asset field called Laptop Issue, connected it to Ticket assets and created a Field called Up to Date Laptop Issue, but the formula the AI keeps giving me doesn't seem to work. 

 

Would the better work around be to have the Asset Table record itself populated the latest Affected Asset Laptop Issue and go from there? Or is there another, easier way that I'm missing entirely.

Best answer by JeffRichey47779

Hi Mickey,

I think you might have more success if you use an Assets table like this:

Make Assets the Parent of Tickets.

Then you can use summary fields in the relationship, in this case maximum Record ID of the child tickets, along with a combined text summary of the issue description from the ticket that matches that maximum record ID. 

NOTE: For this to work, you will also need to pass the maximum record ID back down to the tickets table as a lookup in the relationship. This allows you to create the filtering on the combined text summary field. Record ID = Maximum Record ID. Think of this as the Ticket Record ID making a "round-trip" from the Tickets table to its parent and back.

JeffRichey47779
Forum|alt.badge.img+4

Hi Mickey,

I think you might have more success if you use an Assets table like this:

Make Assets the Parent of Tickets.

Then you can use summary fields in the relationship, in this case maximum Record ID of the child tickets, along with a combined text summary of the issue description from the ticket that matches that maximum record ID. 

NOTE: For this to work, you will also need to pass the maximum record ID back down to the tickets table as a lookup in the relationship. This allows you to create the filtering on the combined text summary field. Record ID = Maximum Record ID. Think of this as the Ticket Record ID making a "round-trip" from the Tickets table to its parent and back.

    Terms & ConditionsAccessibility statement