Form with pages/blocks the signature field was not saved

if I have several pages and blocks in a form and assuming Pag4 contains a signature field, it shows when saving the form that the signature was not saved. The form always jumps to the first page, which I’ve been complaining about for a long time.
When saving a form, the current page should remain displayed after saving. This may also be the problem that the signature is not saved.

The workaround I use is a separate form with which I write the signature separately in this table, but that cannot be the solution.

I use a simple table with various fields, including a longblob field for the signature

Open the Pag
image

edit the Signature field
image

save the form (jumping to first page)
image

go back to signature and the signature field was empty
image

What kind of data type did you use in your tabe?

Hi,
thank you for your response

image

Dear @salvatore,

When we performed some tests in the scenario described by you, we did not identify the two problems reported (empty signature and return to the first tab after saving the form). The tests were performed in the most recent version of Scriptcase (9.9.014(23)).

Can you give us more details so that we can identify the scenario(s) that the problem is occurring?

We are waiting for your feedback.

Best regards!

used by windows edge, firefox and ios (iPad) Safari

this problem has existed for 4 years. At that time I found out that if a field is a many to many field, this problem arises. Of course I still have these many to many fields

i have some many to many relationship. I have now deleted all and then it works as desired. so it must be related to that.

image

image

image

image

image

image

image

image

Any Updates to this case?

Dear @salvatore,

Thanks for your return!

We performed new tests according to the specific scenarios described by you in the same version 9.9.014(23), however, no problems were identified.

Whether with the presence or absence of an N:N relationship, the signature field retains the content even after saving or inserting it, as well as remaining in the same tab where the field is.

If possible, check it in a new blank project, with only 1 form application built on top of the table that contains the longlob field for the signature and 1 simple N:N relationship, the problem continues to persist.

We await your feedback so that we can discover the cause of this impasse that is disturbing you.

Best regards!

I could easily reproduce the problem…

Table EmployeeProfiles


CREATE TABLE EmployeeProfiles (
EmployeeProfileID int AUTO_INCREMENT NOT NULL,
ContactID int,
CompanyID int,
EmployeeShortName varchar(20),
DayOfBirth date,
Signature longblob,
DrivingTeacherNumber decimal,
DefaultStartLocationID int,
DefaultStateID int,
DefaultCityID int,
DefaultDrivingLicenseID int,
DefaultTransmissionID varchar(1),
DefaultPaymentMethodID int,
DefaultLearnControl tinyint(1),
DefaultDrivingRequirementTemplateID int,
DrivingLicenseIDs varchar(255),
/* Schlüssel /
PRIMARY KEY (EmployeeProfileID),
/
Fremdschlüssel */
CONSTRAINT FK_EmployeeProfiles_ContactID
FOREIGN KEY (ContactID)
REFERENCES Contacts(ContactID)
ON DELETE RESTRICT
ON UPDATE RESTRICT
) ENGINE = InnoDB;

CREATE INDEX FK_EmployeeProfiles_ContactID
ON EmployeeProfiles
(ContactID);

CREATE UNIQUE INDEX IDX_EmployeeProfiles_Unicque_EmployeeShortName
ON EmployeeProfiles
(EmployeeShortName);


Table Branches


CREATE TABLE EmployeeProfiles_Branches (
EmployeeProfileID int NOT NULL,
BranchID int NOT NULL,
/* Schlüssel */
PRIMARY KEY (EmployeeProfileID, BranchID)
) ENGINE = InnoDB;


image

image

image

clear signature
image

click Save
image

the form switch to the Pag1
image

look if signature is clear on Pag2 and the signature was not cleared
image

many to many field
image

image

image

image

image

image

image
Field, Title Input all the same

image

image

image

Dear @salvatore,

Thanks for your return more one time!

Please contact us at bugs@scriptcase.net so that we can assist you, and possibly arrange a remote access to take a closer look at this issue to find the cause.

Once again, we thank you for your cooperation and we are here to help you.

Best regards!