RD-Pro: Advanced Lists

Last Updated: 16 Jul 2021


This article describes how lists work, what the actions, conditions and expressiosn related to Reading List do and what types of lists you can build. This involves the following actions, conditions and expressions:




Types of List Data-Structure

Lists must be defined into a specific structure. You can use the BASIC "Write Data-Custom" action to build this structure manually, or in case of Object Type Lists use the PRO "Append List-Data" action to append data at the back of the list.

Object-Type List

This List type is very important and is most commonly used. The data structure must be in the following format:

Here, each Item Parent is actually a JSON object which can contain Keys and Data.

This type of list is used for building chats, posts, friend management, leaderboard, etc.

Value-Type List

This List type is less commonly used. The data structure must be in the following format:

Value-type list querying is only relevant if your items are just values and not JSON objects.


Append List-Data • [Category: Write]

This is only for Object-Type Lists.

Use this action to append data to a list in multiuser applications. This action generates a unique Item Parent Key every time a new item is added. By using these auto-generated keys for each new element in the list, several clients can add Items to the same location at the same time without write conflicts. The unique key generated by this action is based on a timestamp, so list items are automatically ordered chronologically.

The image in the right shows the structure of a Chat Room. Note the Item Parent Keys generated by the "Append List-Data" action.

Read List-Data • [Category: Read List]

This action will start the list reading or fetching process. (You must be familiar with similar actions in the BASIC Plugin such as the "Read Data-User Account" and "Read Data-Custom".)

There are init options for this action which can be used to request sorted and filtered data.



Init Read List Actions [Category: Read List]

Initializing can make the "Read List Data" Action to request sorted and filtered data.

If you want to Initialize your "Read List Data" Action, "Init Read" actions must be specified before each "Read List-Data" action. If you do specify any init options to initialize your "Read List-Data" action, the list you will get will not be filtered, and ordering of data will depend on the Lexicographic Order of Key Names..

Multiple initialization actions can be used for a "Read List-Data" action. But using the same option twice or more will overwrite the previously set options.

There are six initialization actions:


On Append/Write/Replace[Category: Write]

This is triggered when any Write action such as append, write or replace is completed.

On List Change/Read ⁽⁴⁾[Category: Read-List]

This is always triggered when any list has been read successfully.

Also, if "Sync When" is enabled in "Read List-Data" ⁽¹⁾ Action, "On List Change/Read" Condition is triggered according to the Sync method chosen.

On Reach List End[Category: Read-List]

This is triggered when the length of list read is less than the maximum length limit specified in Init Actions: "Limit to First" ⁽³ and "Limit to Last" ⁽³ᶦᶦ

Has Reached List End • [Category: Read-List]

This is the same as the previous one except that this one is a non-trigger condition. 

True when the length of list read is less than the maximum length limit specified in Init Actions: "Limit to First" ⁽³ and "Limit to Last" ⁽³ᶦᶦ


getTagsFromString[Category: List: Both List Types]

Firebase RD Pro Plugin has the options to create and read UserKeys which usually look like userkeyname@0000. An user can tag another person by including his/her UserKey Tag in the stored data. This can be used in a Chat system to Tag users in a message.

The Tags stored in a string data must follow this markup format: "/@userkeyname0000/". (The slashes "/" are important)

The "getTagsFromString" expression accepts a string parameter and then returns a JSON-Array-string of all Tags found in that string.

tagUserKeyArray [Category: List: Object-Type]

Get an array string of tagged users in a list item when TagArray Key ⁽⁵⁾ is mentioned in Read List-Data Action.

The tags stored in the string data must follow the above mentioned markup format.