Dynamically set the min & max entry limit of number field with the value of another form field // Output calculations to parameters, not only fields!

I would like to see the possibility to use the value of a field (which is calculated based on previous user input) as parameter in the limit properties of a number entry field. I'm sure there would be other similar possibilities (e.g. modifying option text on the fly on checkboxes or radio buttons), thus this could be added generally. Right now in the scenario described above, if I type in the reference of the field I want to use as parameter, it doesn't work.

Is it possible that such a thing could be implemented?

I am not sure if I have understood your requirement correctly. 

Do you mean to say that you want to dynamically set the minimum & maximum entry limit of "Number" field?

Unfortunately it is currently not possible to achieve this. I am creating a feature request ticket and forwarding it to our backend team. Please note that creating a feature request ticket does not ensure that this feature will be implemented. It completely depends upon the feasibility and priority of our backend team. We will get back to you as soon as we have any update from them. 

Yes, that is correct. In my case it is the limits of a number entry field which I want to be dependant on a calculation, but I think if it would be implemented, then it should be usable generally to insert data from fields that contain the correct type into the properties of other fields...

It would allow powerful ways to adapt form fields to the user based on previous choices, for example that dropdown list options could contain, for instance, products that would be displayed with a personalized price (e.g. a discount).

I picture it much like the way that you can edit field calculation itself, but simply inserting the {reference} to the desired value would work equally as good for my purposes.

EDIT: On second thought, this could be implemented the other way round: that calculations could not only be output to fields, but also to their parameters. Like that there wouldn't be need to extend the interface for the field parameters.

Thank you for the clarification. We have added that information to the feature request ticket. Once this is made possible in the future, you will be informed here.

Thank you.