Dynamic value in a database field?

Question
1

Can a database field have a dynamic value based on something else? or the values in the database is all static?

Sometimes you would want a value in the database to reference something else, and change in real time when the “something else” changes, the same way that you have the ability to tell a text element default value to reflect dynamically a field in the database.

Otherwise you always need to create a separate action to change the value of the field at the point of entry, modification or deletion.

1 Like
2

Hi,
I may not have understood your question, so this may not be what you want, but just in case, you may want to check if this helps you:

3

I’m not sure if I understood correctly, or if I am amble to explain it properly, but here goes:

You can have two main databases:
A
B(review in my picture example)

Each of them has its own fields like:
A

  • user
  • business
  • notes
    B(review in my picture example)
  • phone type
  • operating system
  • fuel

Now you want to add a new ‘dynamic database’

You will create under
A
a new database that will read from B(review in my picture example)'s field like this:
A

  • user
  • business
  • notes
  • TEST
    51
    Screen Shot 2017-11-21 at 01.41.51.png718×428 16.6 KB

    Where at Field name it will be TEST, and at field type it will be B(review in my picture example). Check the box to be multiple entries.
    Now you will have a a field in A named TEST that will contain the fields from B (and those are phone type, operating system and fuel.

It will look like this, under A:
TEST is a list of B(review in my picture example)
So when you will use the Test to pull data, you can choose whatever fields from B(review in my picture example) you want, like you can remove the fuel (unselect it) and only use phone type and operating system.

Does that make any sense? haha. Sorry, I hope it does, if not, I can connect to your editor and we will try to do it together over a Skype call.

4

OK, finally i figured out the answer, you would use a “Do when condition is true”!

So if for example you want to change a users status to “yes” on a boolean field whenever that user meets a criteria, - regardless of which button or workflow triggered it -, you use the “Do when condition is true” “only when” current user’s… and use an action to change the user boolean to “yes”.

This way, the database change is not triggered by a specific button hit by the user, but rather by a condition, so you dont have to write this action on every point of entry, edit, or deletion that effects this condition.

Sometime you realize what problem a function solves only by having the problem…