Formula field to count # of records
Parent Tables: Nodes and Power Permits. Child Table called Poles. Want to get a count of Power Permits per Node. When I create a Summary report I can group by Node and then by Power Permit and manu...
Forum Discussion
I think that you will need to create a table called Node-Permits where the Key field looks like this
DF012-23556149
You can populate it initially by making a formula field on your details table and then making a summary report on that field and then using More ... to copy to another table.
Then you can make that table a child of the Nodes table by making the field DF012 on that table by formula off the field containing DF012-23556149
so like Left([Node-Permit],"-")
and using that to be a link to Nodes. Then make a summary of the # of Note-Permits.
But then you will need to auto maintain that Node-Permit table so the app knows to add new records when one does not exists. You can make an action to do that when the parent does not exists. The Table Node Permits would need to be a Parent to your most detail table and you can create a field in Node Permits which always calculates to true like [Node permit exists?] with a formula of
true.
Then look that up down to the detail table. then fire an action to create the parent record if it does not exists. I also suggest making a safety net subscription report to detect of there are detail records and that Node Permit record did not get created by the Action - in case it fails from time to time.
DF012-23556149
You can populate it initially by making a formula field on your details table and then making a summary report on that field and then using More ... to copy to another table.
Then you can make that table a child of the Nodes table by making the field DF012 on that table by formula off the field containing DF012-23556149
so like Left([Node-Permit],"-")
and using that to be a link to Nodes. Then make a summary of the # of Note-Permits.
But then you will need to auto maintain that Node-Permit table so the app knows to add new records when one does not exists. You can make an action to do that when the parent does not exists. The Table Node Permits would need to be a Parent to your most detail table and you can create a field in Node Permits which always calculates to true like [Node permit exists?] with a formula of
true.
Then look that up down to the detail table. then fire an action to create the parent record if it does not exists. I also suggest making a safety net subscription report to detect of there are detail records and that Node Permit record did not get created by the Action - in case it fails from time to time.