So that his challenge does not get lost in the weeks, with this post, I’m pulling out of the thread the first challenge, which was graciously provided by @Markoconnor.
June 2022 TBX Challenge
Create a tbx file from the data that creates all managers and employees as a built in Person Prototype
Add $Attributes that capture age, company, salary inside the Person Prototype
Managers and Employees are to have different badges
Background outline colour to be different if Age >50
Create an Agent that picks out the company with the most employees
Create a ‘dashboard’ note that displays the average salary of all employees
Here is my version ( I purposely haven’'t looked at yours but looking forward to doing so shortly to compare appproaches )
I have included a note MySteps detailing the steps I took ( most of whch were to tweak the spreadsheet into a more useful arrangement prior to copy and pasting by adding columns for Prototype Manager and Employee and chaning headers to Name)
I used Attrtibute browser rather than an agent to get to the Company with most employees
Very cool. Yes, we took different approached. Mine was around creating a dynamic file automation rules rather than using stamps, which was what your approach used. We did similar cleanup in the Excel. I thought of using the Attribute Browser too, but wanted to stay true to your challenge.
Just looked at yours - nice - Interesting differences too - I actually couldn’t work out my own challenge to the “agent for the largest company” in the time I’d allotted to do it. I rarely use the Attribute browser ( I wondered if cross tabs might be useful here but use that not at all so stopped playing with it ) - Your code in threads passim re terms, links and acronyms etc… I have found very helpful so shall add your agent solution to my snippets pile - thanks
The excel trick of adding a column header ‘Prototype’ with all subsequent row entries the protoype you have already created made the allocation of prototypes to employees and managers trivial ( Using separate select cut and paste operations for both rahter than drag)
Basing new prototypes ( manager/employee) on a base prototype ( inbuilt Person) is useful for not re-inventing the wheel of key atributes while allowing little differences ( like badges )
I tend to reach for stamps rather than rules/edicts as it feels simpler to undo mistakes and can practice on one or two notes without the irritation I often make of adjusting the rule in a note rather than its prototype.