Announcement

**Isomorphic** · 5 Aug 2025, 09:58

When you declare a binary field in the DataSource, two other fields are implicitly created to hold the fileSize and fileName. You can also declare them yourself.

These look like validation errors on those fields, as if they were declared required=true, which would be a declaration that probably doesn't make sense, since the values of these fields are dynamically determined during the upload process.

**Blama** · 5 Aug 2025, 12:42

Hi Isomorphic,

thanks for the fast answer. You are right about the required=true. Removing it makes the two validate requests succeed, but they were still there.
I then checked for other validators and I do have a serverCustom-validator on one of my extra fields. I removed that validator for a test and the two requests disappeared.
So now I have two issues:

Why are there two requests and not one? (Minor to me, but will create a testcase)
What is it with the serverside exception? As the validator is there for a reason I will always have a validate request (or two). Could you have a look if you see anything suspicious about the log from #1?

Thank you & Best regards
Blama

**Isomorphic** · 5 Aug 2025, 16:49

The double validate request is likely a subtle missing performance optimization, so yes, a test case would be great.

Then as far as the exception, if it's gone away, it's likely because we weren't expecting a validation request with a binary file (because those related fileSize / fileName fields should not be marked required), and we tried to treat it as another class of request, where binary is submitted as base64. This is probably more of a curiosity than something needing a fix, but if we had a test case for that, too, we could take a look.

**Blama** · 6 Aug 2025, 03:30

Hi Isomorphic,

OK, will create a testcase. The field and validator look like this. Perhaps this is already enough to give you an idea.

Code:

<field name="ATTACHMENTTYPE_ID" type="integer" foreignKey="T_ATTACHMENTTYPE.ID" displayField="ATTACHMENTTYPE_NAME_TRANSLATED" joinType="outer">
            <title><fmt:message key="type" /></title>
            <validators>
                <validator type="serverCustom" serverOnly="true">
                    <serverObject lookupStyle="new" className="com.lmscompany.lms.server.worker.validator.ValidatorAttachmentType" />
                    <errorMessage>$errorMessage</errorMessage>
                    <applyWhen operator="and">
                        <criteria>
                            <criterion fieldName="LEAD_ID" operator="notNull" />
                        </criteria>
                    </applyWhen>
                    <dependentFields>
                        <dependentField>DATA_FILENAME</dependentField>
                    </dependentFields>
                </validator>
            </validators>
        </field>

Regarding the serverside exception this is still an issue for me, as one validate request is expected because of my validator, just not two. So if you could look into the possibly wrong base64 path, that would be great.

I'm off for vacation on Friday, so I wont be able to create a testcase here just now, but perhaps this is already enough information?

Best regards
Blama

**Blama** · 26 Aug 2025, 02:25

Hi Isomorphic,

I was able to reproduce locally in downloaded https://smartclient.com/builds/Smart...val/2025-07-29
I change the title field in mediaLibrary.ds.xml in the upload sample (v12.1p_2025-07-29) to this:

Code:

<field name="title" title="titel2">
    <validators>
        <validator type="isUnique" serverOnly="true">
        </validator>
    </validators>
</field>

Then if you try to upload this test PDF file (from here: https://www.sbr.gov.au/sites/default...20document.pdf), you'll see the following problems:

operationType:"validate" request has a Transport error and the exception from #1 in the server logs
Whether the validate requests ends with a Transport error, a Validation error or a success - there is always an add-Request afterwards. It's only expected in the last case.

Best regards
Blama

Attached Files

Test PDF document.pdf (3.0 KB, 17 views)

**Blama** · 26 Aug 2025, 02:29

Hi Isomorphic,

for whatever reason the filename also seems to be important. It does only happen when the file is named "Test PDF document.pdf". As "Test PDF document(1).pdf" it seems not to create the the same problem, even though the content is identical (I just tried again with the file downloaded from #6 to make sure the issue will happen for you as well and Windows renamed the downloaded file).

Best regards
Blama

**Blama** · 27 Aug 2025, 03:43

Originally posted by Isomorphic View Post

The double validate request is likely a subtle missing performance optimization, so yes, a test case would be great.

Hi Isomorphic,

the 2nd request is most likely because the ClickHandler code for my save button looks like this for whatever reason:

Code:

saveBI.addClickHandler(new ClickHandler() {
                public void onClick(ClickEvent event) {
                    if (UploadForm.this.validate()) {
                        UploadForm.this.saveData(new DSCallback() {

So the only problem left here is the server side exception from #6.

Best regards
Blama

**Blama** · 17 Sep 2025, 02:02

Hi Isomorphic,

could you reproduce the issue from #6?

Best regards
Blama

Announcement

12.1p FileUpload serverside exception question

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment