0

How to Create Checklists / Tasks

I've just published a blog post called 'Creating Checklists in Ninox' which you can see here:

 

http://software.kirknessassociates.com/blog_files/e7d4179b07c6bcb203ae50a5b26e828f-42.html 

 

Now, this may seem like a 'random' topic to choose, but I had previously written posts about how to do this with another database (I won't name it here) - which required the use of either Zapier or Integromat - both of which proved quite clumsy. Ninox's language is able to handle this easily and highlights the power of this platform.

I also think that this provides a useful worked example of using NX to read and create multiple records and the principle can be applied to other use cases. You can download the database from within the post.

6 replies

null
    • Mconneen
    • 4 yrs ago
    • Reported - view

    Thanks Julian, 

    I am a David Allen "Getting Things Done" (GTD) fan.. though I struggle to consistently implement it.  I purchased a "vendor product" that implements this and helps me "focus" (hint hint on Mac Product)..  It is very good.. but I have to purchase a Mac version, and iPad version .. an iPhone version ..  Implementing something like this in Ninox would give me all platforms.. :) 

    So.. playing around with the Kanban view .. as well as grouped views.. I am on my why to eliminating another Commercial Off The Shelf (COTS) applicaiton that I pay an annual subscription ... makeing that $100 UDS annual for Ninox even that much more beneficial! ;) 

    • Holly_M
    • 1 yr ago
    • Reported - view

    I just found this article and if I want to have multiple checklists, where depending on the stage, the record can have a different checklist applied. Would I need to create a table for each checklist or can that be done with a single table?

    • Fred
    • 1 yr ago
    • Reported - view

    Hi Holly M -

    Without knowing anything about your DB, all I can say is yes you can do it in 1 table.

    May I recommend that you create a table, we can call it ChecklistChoices. Then create at least the two fields, a choice field called category or level or something like that and the other could be a text field called Item.

    Then in your other table you would create a dynamic choice field that looks to the above table and filters for the choices you want.

    May I also recommend that you start a new post instead of adding to a post that is 3 years old. Three years ago there were no dynamic choice fields.

    • Smartin
    • 1 yr ago
    • Reported - view

    Here is what I would like to do: Create a checklist for a collection.

    The collection includes Base items that are numbered.

    Then there are "variations" on the Base items. For example, in addition to base items there are those that are red, or green, or orange.  So there could be an item 1Red, 1Green, 1Orange.  And within the 1Red, there are only 250 in circulation with these receiving a sub serial number ... so this would be 1Red 99 of 250 for example.  Green variations could be 1Green 33 of 50 as another example.

    This pattern would repeat every year. So there is this situation for 2022, 2021... and so on... worth collecting and adding to the checklist continuously.

    There are thousands of these items to collect, so loading the base list via a CSV is a good start. But there is no list available for upload with all of the permutations. 

    HOW DOES ONE CREATE A CHECKLIST OF ALL THE PERMUTATIONS IN NINOX! I would assume making a Base Table, and then a variations table is a good idea because the variations change every year. So how does one assemble this? HELP!

      • Fred
      • 1 yr ago
      • Reported - view

      Smartin Your question deserves its own post. It sounds like more of a record creation process.

      Though you may want to rethink the checklist idea as having a checklist with hundreds or thousands of choices I find unmanagable.

    • Smartin
    • 1 yr ago
    • Reported - view

    Fred - further context is that this goes with a trading card database, and the hobby sort of revolves around checklists.

    There is a total universe of cards printed, with individual variations. Do you have the variations in your collection? That's where the checklist comes in... check if you have it, uncheck if you don't! 

    The trick is that there are numerous examples where a 'base' card has the same serial number in the set even though it is a "Red" or a "Green" or an "Orange" etc variant.  The hobby also is prone to just making checklist after checklist. A collector should have his own master checklist of course!

    So this is not really about maintaining or selecting choices...it's more about efficiently aggregating a bunch of related checklists into one master checklist.

Content aside

  • 1 yr agoLast active
  • 6Replies
  • 2101Views
  • 3 Following