Report Error Issue

pbrad

Hi,

I am running into an issue with REPORT ERROR in V4 and I am wondering if I am looking at it the wrong way?

I am having an issue where I am creating a record using ENTER NEW and that object has a rule that uses REPORT ERROR if certain conditions are met. If the user then decides to hit the cancel button after they see the error the object is created even though they cancelled it. Even if the object has required fields, the object will be created without those fields populated.

Steps to recreate using a simple blank bsv:

Create a process where the rule is 'ENTER NEW RegularUser USING Main'
Run the process, enter 'admin' as a LoginName, try to save the record, view the default duplicate loginname error message and then hit the cancel button.
Search for RegularUser and you will see that there are now two RegularUsers with the LoginName 'admin'.

When viewing the database, it is apparent that the second object is created on the running of the REPORT ERROR process which is contrary to my understanding of what a REPORT ERROR process should do.

This is causing a real issue for me, is this the correct functionality of REPORT ERROR? If so, is there a workaround that would prevent this problem?

Thanks as always,
Pete

aware_support

Have you read the section about transactions in the User Manual? This may have some answers for you (maybe not).

It really depends on where the REPORT ERROR is issued. Consider this:

Scenario A:
ENTER NEW MyObject
(MyObject has rules that invoke REPORT ERROR actions)

Scenario B:
ENTER NEW MyObject
CREATE MyObject2
(MyObject2 has rules that invoke REPORT ERROR action)

If the error has been raised by rules of the object MyObject in scenario A, the instance of MyObject SHOULD NOT be created (unless there is a bug)

If the error has been raised by rules of the object MyObject2 in scenario B the instance of MyObject WILL be created because it is preceded with a rule that invokes the user interface.

pbrad

I think that my example is a pretty clear case of Scenario A. There is no second object.

Just try creating a regular user in any business space that you have with a username of admin, cancel out of the object after you see the error message and you will see that the object was created anyway.

aware_support

We'll check it out right away and if it's a bug we'll fix it for the next build.

pbrad

Much appreciated.

Thanks, Pete

aware_support

Just checked it out and everything seems to work properly. What database are you using?

pbrad

MySQL

aware_support

Checked MySQL 5.0 - everything is working fine.

Which version of MySQL are you using?

pbrad

Hi,

I am running mysql 5.0 locally via xampp on my development laptop. I have tried to duplicate the problem on my production server and it works fine there. I guess that it must be a xampp issue perhaps.

Anyway, it is definitely creating database records when the Report Error runs locally but doesn't on the server and that is where it matters so I guess that I will just live with it locally.

Thanks,
Pete