Function on value change for a file field

fmvalsera

Hi all,
working with v3.8.6 I have create a relation with an attribute of 'file' type. Then, in a form I have added the field related to the attribute and set the 'Function on value change' to a frontend function which is calling the instance function app.record_save();

In this scenario, the frontend function is called after uploading a file (pressing the "Add" button), but the record is not saved.

Adding a second dummy attribute to the relation and setting the same frontend function as "on value change", the record is saved when a type an input in the dummy field.

Is this a bug or an expected behavior?

Thanks for your help.

gabriel

File attributes are a bit tricky, because they need to work very differently to other attribute types.

Maybe the function call is executed before the file has been uploaded - the field, if it is a required field, would then be marked as empty and the form save would fail. But I would need to check if this is the case. I´ll let you know.

gabriel

I´ve done some testing and it worked for me in all cases:

Whenever a file was added, regardless how long it took, the function was called after the file upload succeeded - and it saved the form correctly after.

Do you have any other fields on your form that might interfere? Stuff like fields that are hidden, but which values might be required to create the record?

For testing, you could create a small form just with the files attribute input, like I did. If that still does not work, we at least know, it has no external reason.

fmvalsera

Thanks, Gabriel. You are so helpful as always.

I think that the problem is that I have my file attribute defined as "must have value" in the relation. Additionally I set the max size/length in the associated field in the form to 1.

After disabling the "must have value" it works fine, as expected. The function to save the record is called after adding a file, and the record is stored properly.

Should this use case be supported with "must have value" enabled, or is there any reason to allow always NULL for this kind of attribute (file)?

Thanks for your time!

gabriel

This is quite weird - it works for me even if the attribute is required. Have you made a test form with just the file input on it - to make sure that nothing else might be at fault?