I need to save a pile of JSON in a node I'm publishing (this is for FlexDash and the data is the configuration of the dashboard). I'm a bit at a loss about the best method for saving. I've contemplated three options: Use a persistent context store. The mechanics are fairly simple, but rather user…

[image] knolleary: But another important point is the flow file should only get updated when a user hits Deploy [image] knolleary: [image] tve: Is there a way for a node to mark itself as modified Not from the runtime. In the editor, yes. Aren't you saying that there is a flow …

[image] tve: Aren't you saying that there is a flow API to modify the flow, but that the flow should should not actually be modified unless the user hits deploy, and that it's not possible to cause the deploy button to be activated? Or are you saying that anything that modifies the flow needs to…

[image] dceejay: if you look at a flow using the dashboard then you will see the ui-base node there with all the theme and site setup in it. Similar to any (for example) mqtt-broker definitions etc... Config nodes are a "known" thing so when you export a flow from a tab then we make sure that a…

It’s certainly a pile of “something” :wink: From your point of view you may also have multiple config nodes if you are going to have multiple endpoints/sites

[image] dceejay: From your point of view you may also have multiple config nodes if you are going to have multiple endpoints/sites Yup! And as far as I know (very little...) there's no way to hook into the import process, e.g. to provide a choice about which endpoint/site to merge the flexdas…

[image] tve: the data is the configuration of the dashboard Hi @tve , Then I have misinterpreted this until now. Because in the original discussion you wrote : You insert data into a data structure (a tree) on the Node-RED side. That is reflected to a tree in the front-end. A widget is then …

[image] BartButenaers: But now it is not clear to me anymore which of those 3 types of information are inside your tree, and which of those needs to be persisted? Your static config is already persisted in the flow.json file via the node properties. Well, all the data is in one big json tree …

[image] tve: The configuration sub-tree needs to be persisted Does it work (roughly) like below then? The user enters static config in the config screens of the fd nodes. He clicks the 'Deploy' button, so the static config is stored automatically in the flow.json file. Then the static confi…

Right now things are a bit messy... It's something like: The edit form in NR is populated with the values in the flow.json You make changes and hit deploy NR persists the changed config map to flow.json The fd-whatever node constructor is called with the config map, it possibly adjusts fields, and…

Ok, thanks for the update!! Have tried to visualize it a bit, so I - and hopefully other people - can imagine what your setup looks like: [image] Feel free to start painting on it if something is not correct or missing! If I understood everything correctly, the red part is what you need to pers…

Node-RED

Node-RED Forum

Where to save persistent data in a published node

Developing Nodes

berijan 13 March 2022 07:09 24

This may help you

https://nodered.org/docs/user-guide/context

Topic		Replies	Views
Save/restore state of dashboard input elements Dashboard	38	2268	4 April 2021
:question: DISCUSSION: Should nodes save/restore their own context? General	97	4757	12 November 2020
How can a node update its own config/params? Developing Nodes	8	600	3 June 2022
A guide to understanding 'Persistent Context' General	90	45673	31 August 2022
`template` node. Not understanding all that is written General	36	1758	28 December 2019

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Where to save persistent data in a published node

Related topics