Splitting, totaling, and reporting of loads by ""Shareholder

I have written a complex app for dealing with crop yields and the whole cycle of planting to harvesting and Sections, Fields  and Shareholder splits.  I suggest that you contact me to see if it might be modified to fit your farm management needs.  QuickBaseCoach.com

We have an app that is formatted to suit the needs we have.  We are just needing to figure out how to link up the Shareholder table to get the reports for the splits for each parcel.

This will either need to be done by a developer using script or it may also be able to be done natively depending on your app structure. I focus on native solutions and make use of techniques using API_RunImport to create multiple records.  For example to create the Shareholder Split Load records as a child record to the Load record.  The sum of the splits would balance to the Load Total Bushels

But either way, it's a complicated answer which would require someone looking at your app and is likely beyond the scope of question that you are likely to get an answer on this Forum.

If I had to guess I would say to do this natively perhaps a table in between loads and shareholders called load shares or something. That table would handle the splits. You'd also be able to report on those splits and also prevent users from adding more than 100% of a load.

Right, it needs a loads Splits table, and the trick is to make a URL formula button to create the correct number of splits and assign them to the corect shareholder.

We would need to understand where the info is recorded as to the shareholders involved in each load. Is that done on a child table already or just a few fields on the load record done manually per load or how? That is the missing information so far in this question.

Created Prototype Screenshot.



Neal
NealPatil @ gmx.com

We have a table for "Entities" and a table for "leases" that is linked in a many to many format through a tabled called shareholders.  The Lease table is connected to the "parcels" table.  A Lease may have many parcels and many entities.  The shareholders table is then linked to a "load shares" table and the "loads" table is connected to the the "Load Shares" Table.  The loads are linked to a "crop zone" table which is then linked back to the "parcels" table that the "leases" table is linked too.  A parcel can have many crops in a year, and a crop will have many loads in a year.  The Load Shares table currently allows us to "Make a new Load Share"  where we can select the related lease, and then select the related Load.  So in this setup we have to select each entity that is in a lease and each load that the lease applies to manually as an entry into the "Load Shares" table.  We either need to automate this process, or rearrange how we are linking the information together.  Maybe the attached diagram will help with how we have it setup at this point.  

I am wondering about making the "Leases" table be the many to many table between entities and parcels.  (Again A Lease may have many entities and many parcels)  Then we would have "A Lease" that could own many loads based on the parcel name that also owns the load?  Have not tried that yet.  Thoughts?


Thanks for the help so far!!

I believe I know how to automate the split button using only native code. We will be able to sort this out I see your app on Monday.

There is a technique where we can put focus on a load. That will intern put focus on the parcel in the parcel will put focus on the lease and the lease then put the focus on the shareholders who own that lease.

Then we will use API_Run import to import say those three shareholders of the respective percentages into the load shares table.

I would like to thank Trinity for automating our solution for us.  They were able to save us a lot time going forward with the app.

Glad that my recommendation to try Trinity worked out for you.  When we spoke I realized that you needed the the split to happen by being initiated with a Webhook and that required a script.