delete a record at detail tab it affect to parent, make a warning message about refresh

Description

None

Environment

None

Attachments

3
  • 22 Aug 2020, 02:54 PM
  • 17 Jul 2014, 03:20 AM
  • 17 Jul 2014, 03:20 AM

Activity

Show:

zuhri utama July 7, 2023 at 2:08 AM

Triaged by Zuhri Utama

This is reproducible in 11.

i think the popup message is ok. this is the warning message but the problem is the warning message is displayed as error message with red box popup. it make user think that this is problem and need action to check. my suggestion is change the popup message layout by change the color to yellow that suitable to show warning instead red that related to error.

as reported by , the message only occur when the action affected the parent tab. so, the behaviour is not a problem. only need to change how warning message is displayed.

i checked on org.compiere.model.GridTab line 1014 that the warning is using saveError instead saveWarning but when i tried change to saveWarning, the popup is not appeared. is there any clue where i need to check how popup is displayed?

Diego Ruiz August 22, 2020 at 2:54 PM

Triaged by Diego Ruiz,

This is reproducible in 7 .1z. The system behaves like that when the parent record has a field that gets updated when the detail records are changed. For example, you can delete substitute records in the product window and the system won’t show the dialog. But when you delete a record in Invoice Payment Schedule > Payment Schedule that affects the Pay Schedule Valid flag in the parent tab, the dialog pops up. See the video for more information.

Hiep Lq July 17, 2014 at 7:19 PM

not easy to fix this.
hard part relate current behavior. We can edit parent record and delete or edit detail record at same time:
analyse below condition:

1. edit a header record.
2. focus to detail tab to edit or delete (example delete a detail record).

below is step process:
3. delete selected detail record (this action make a change to parent record in database)
4. navigate to next detail record
5. check header is have change
6. save header record

solution 1: after step 3, process refresh parent tab => remove message about but change in step 1 is lost
solution 2: after step 3, don't process refresh parent tab => have message as attach image, and data in step 1 is can't save (because conflict state) user must manual refresh parent tab to continue
solution 3: after step 6, process refresh parent tab (current behavior) => have message as attach image, data change in step 1 is lost, user can continue without manual refresh parent tab.

solution 4: remove behavior "We can edit parent record and delete or edit detail record at same time"
before edit or delete detail record must save parent record (auto commit or manual save)

I think solution 4 is suitable.
or i need your suggest in this case. please help me.

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created July 17, 2014 at 3:20 AM
Updated July 7, 2023 at 2:08 AM

Flag notifications