Need to be able to calculate the total of column data in order to be used in reporting metrics

Well, the sum() function can do that for you.

Can you explain how though because I tried that and it didn't work. It's not as simple as entering =sum(recordtype!dcloans.fields.principlebalance) somewhere? Or even if it is, where would you use that formula?

Well. You need to use the actual values, not just a reference to some field in a record.

=sum(local!YOUR_DATA[recordtype!dcloans.fields.principlebalance])

Ok, I know this is a pain, but I am still trying to learn this stuff and I am really under the gun here so I could really use some hand holding here. To start, where would you create that local variable to capture the principal balance data? And would it be local!principalBalance?

Next question would be, where would you put that sum formula to display the result?

The variable you are using to hold the grid data use that same variable in the sum function and for referencing the field to be used inside sum we use recordtype!recordName.fields.columnName
Once you type recordtype! you will get the necessary fields.
(The above solution is when you are using records to fetch data, in case using cdt use index function inside sum instead index(arraywithdata,"columnName",{})

I need to be able to display all this information on a reports interface, so can't I create some sort of GetPrincipleBalance query that grabs all that data from the various records and then utilize that result in a sum function somehow?

You'd have to retrieve the info in a query (separate from the grid) and put it in a local variable.

You would put whereever you need to display it. In a grid field sourced by Record Data it's a little tricky. I would suggest creating a small area under your grid to display the sums/balances etc.

Something that looks like this maybe?

docs.appian.com/.../data-value-display.html

docs.appian.com/.../reference-records.html

Ok, so let's forget about the picture of the grid that I posted, seems maybe that is throwing things off track, I only posted that to show that I have records of info I need to pull from. What I am trying to create is an interface, with some sort of components on it that will display the result of pulling the record data from the Principle Balance and Bid Amount fields and total each. There won't be any grids of data on the interface to use a local variables for or any data entry to be made. I just need to pull the data that has already been entered during the creation of the records, hence the query record idea? Does that make more sense or less?

Ok, so let's forget about the picture of the grid that I posted, seems maybe that is throwing things off track, I only posted that to show that I have records of info I need to pull from. What I am trying to create is an interface, with some sort of components on it that will display the result of pulling the record data from the Principle Balance and Bid Amount fields and total each. There won't be any grids of data on the interface to use a local variables for or any data entry to be made. I just need to pull the data that has already been entered during the creation of the records, hence the query record idea? Does that make more sense or less?

It is really difficult to follow you...

Maybe you want to start with a separate expression rule that uses a!queryRecordType to fetch and aggregate the data. Tune it so it creates the output you expect. Use the Query Editor to get started.

Once this is done, find a way to display that data to the user.

I have this following query which that kind of gives me the result I want (pictured below) but how do I mold the expression so that I can use the result to sum the balances?

a!queryRecordType(
  recordType: 'recordType!{6e4edeaf-030d-4fc2-917a-ab20f1027418}DC Loans',
  fields: {
    'recordType!{6e4edeaf-030d-4fc2-917a-ab20f1027418}DC Loans.fields.{fc4aaffb-28af-4b3f-bd19-a59e7625372b}principalBalance',
  },
  pagingInfo: a!pagingInfo(
    startIndex: 1,
    batchSize: 100,
    sort: 
      a!sortInfo(
        field: 'recordType!{6e4edeaf-030d-4fc2-917a-ab20f1027418}DC Loans.fields.{fc4aaffb-28af-4b3f-bd19-a59e7625372b}principalBalance',
        ascending: true
      )
      )
      ).data

docs.appian.com/.../Query_Recipes.html

docs.appian.com/.../Query_Recipes.html

I know, I am sorry, my brain is fried and I am extremely frustrated that I can't figure this out. I appreciate everyone's patience.

Pressure is not your friend when learning something new.

Just use the query editor to create that query.

docs.appian.com/.../using-the-query-editor.html

I have been trying to come up with the correct query for hours now and cannot get past getting the list of balances. None of the recipes on that line you provided seem to get me where I need to be.

I have tried so many different combinations of queries my head is spinning. If anyone has an idea of what the query and sum function should be to pull all of the data from the Principle Balance filed in a Loans table so that it can then be summed, please post it.

cls5469 said:

this following query which that kind of gives me the result I want

1) store the result of that query in a local variable

2) call sum() on that result (or the relevant field)

First you need to know how to access the field in RecordType data post querying.  Kinda-stupidly, this requires referencing the entire recordtype and then the relevant fieldname.  For the recordtype here in my example I have a field name called "dataLength". (Querying just a page of 10 only for simplicity's sake).

So let's display the full value first:

Traditional queries would let us just add ".dataLength" after that to get the property alone as a list.  Let's try:

(Womp, womp...)

So how do we access it?  Following the error message, we add the record type property reference in square brackets:

Voila!

Then for the cherry on top, since now we just have an array of integers, we can pass that quite cleanly into sum().

Though I often prefer to abstract the individual steps into their own local variables, which adds a bit more flexibility...

And as with most things, when crafting expressions it's best to start with something small and working, and then iterate it step-by-step.

Mike, this is exactly what I was looking for, thank you! !!

I was able to take this rule and plug it into a text field on a interface and format it as currency and it worked perfectly, thanks again for walking me through it like that!

And thanks again to everyone else who provided ideas and and suggestion, I am very grateful for your efforts!