In this meeting, State Changers discuss a data manipulation problem related to comparing and displaying user reports of test scores using Xano. A user's current score would be compared to their previous score, and the percentage difference would be displayed. The scores would be sorted from the most recent first and are related to specific quiz weeks such as week 3, 6, and 12.
The State Changers decided against displaying the differences at the data-fetch stage, in favor of a more flexible, user-oriented approach. They introduced the idea of additional calculated fields, which include the scores' proportional differences, setting this data manipulation closer to the point of delivery. They proposed a method of handling the data which involves creating a loop in Xano, iterating over the scores, and comparing each item in the array with the one following it. In addition, they contemplated whether to use 'time created' or 'term logic' to sort the tests. The data was not consistently adjacent, which originally led to an assumption in the solution, prompting a problem-solving reboot. To find the first condition matching element, they decided on setting up a for-each loop using a 'find first element' filter. While no specific platform like "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", or "AI21" is mentioned in the discussion, the process of down-to-detail-level problem-solving provides valuable insights for software developers and data handlers dealing with similar data manipulation issues.
(Source: Office Hours 7/21/2023 )
