One changes the quantity; another saves from an old form
Two people open the same order. One changes the quantity; the other corrects the delivery date using the form they already had open. What should be saved? Before commissioning custom software, agree that one change must not silently erase another. This guide proposes a worksheet and checks for resolving the conflict, including when different fields were edited.
Adaris’s Custom software service starts with a specific process and agreed checks. The example below helps scope that work: it does not describe an installed application, a feature included in every project or an outcome achieved for clients.
A fictional order with two conflicting proposals
All data is invented. Elena and Mario open order P-208, starting version A: 12 countertop display stands for Tuesday delivery. Elena proposes 18 units and saves first; for this exercise, assume the current record becomes B: 18 units, Tuesday. Mario still sees A and wants to move delivery to Wednesday. His old form contains 12 units, Wednesday.
Do not assume that 18 units on Wednesday is valid simply by combining the changes. Quantity and date being different fields does not establish that the combined commitment can be met. The responsible person must confirm the whole order with the appropriate parties; this guide does not calculate capacity or accept commercial commitments.
| Stage | Record or proposal | Decision still needed |
|---|---|---|
| Starting A, opened by both | 12 units; Tuesday | Identify that both started from A. |
| Elena’s save, assumed B | 18 units; Tuesday | Preserve the reference for this change. |
| Mario’s proposal based on A | 12 units; Wednesday | Detect that his starting point has changed. |
| After comparison | Outcome still to be agreed | Confirm quantity and date together before saving the decision. |
Choose the working rule before the warning message
For this pilot, we propose stopping a save based on an outdated record, retaining the proposal without applying it and showing which current value changed. The person then compares the current order with their proposal and decides whether to revise it, discard it or request confirmation. These are criteria to design and test, not instructions for clicking buttons in your existing application.
Another option to assess is reserving editing for one person at a time. That also needs rules for leaving a session, releasing the reservation and handling an absence. Assigning fields to departments is a third option, but does not by itself resolve dependencies such as quantity and date. Choose according to the process, acceptable waits and decision ownership; checking whether a record changed does not require AI.
For P-208, the proposed behaviour leaves B unchanged while Mario reviews. It does not mark his change as saved or automatically reapply his form. The final quantity and date remain subject to a human decision. Also agree where the proposal is retained and who can see it: a business-data copy must not be left unprotected.
Two references that show why you need to ask
AppSheet’s help explains that when two clients change the same row at nearly the same time, the last client’s change persists. The Power Fx Errors reference describes edit conflicts and warns that Power Apps does not attempt to detect them for changes to Dataverse tables. Behaviour depends on the system and data source; support for multiple users alone is insufficient.
These references help frame questions; they establish neither compatibility with Adaris nor a complete platform comparison. Ask for a demonstration of the specific workflow using your configuration. A history that supports later investigation and a protection that stops an outdated save are different requirements; specify which you need.
Prepare inputs without handing over customer data
Bring a fictional initial record, two separate changes and the order in which saves are attempted. Add the roles: who changes quantity, who proposes the date and who confirms the combination. Use invented names and references; credentials and real orders are unnecessary to explain the problem.
For each attempt, note the starting version, the fields the person intended to change, the current record encountered and the observed outcome. Include which proposal could be recovered, who resolved the difference and what remained pending. Keep only necessary information with agreed access and retention. A “saved” screenshot does not replace reopening the record and comparing its values.
A small pilot that actually tests overlapping edits
Agree one order type, two editing roles and an acceptance owner with Adaris. Prepare the following cases in an authorised test environment using fictional data. The columns describe what to check; they do not claim anything has already been built or passed.
| Prepared case | Response to evaluate | Evidence to retain |
|---|---|---|
| Both change quantity from A | The first save is not silently lost; the second requires resolving the difference. | Before/after values, warning, pending proposal and final read. |
| Elena changes quantity and Mario changes date | The whole combination is reviewed; a valid merge is not assumed. | A, B and old proposal distinguished; responsible person’s decision. |
| A tab stays open with A | The starting point is checked when saving, even if opened earlier. | Which record was current and what happened to the proposal. |
| The role cannot change quantity | The operation is rejected without changing the order or exposing unrelated information. | Authorised test attempt and subsequent read with an appropriate role. |
| Save confirmation does not arrive | Success is not announced without checking; state is queried through the agreed route before retrying. | Attempt, later query and outcome or remaining uncertainty. |
Measure observations and keep unresolved cases visible
Record the number of attempts, differences detected, proposals recovered and the time a person took to resolve each case. Separately check whether any previously confirmed value disappeared without warning. Keep the cases and conditions alongside each measure; no improvement figures or success rates are reported here.
The trial should provide evidence for a decision. If a proposal is lost, permissions are not respected or the final state cannot be checked, leave that case pending and address its cause before accepting it. Agree criteria, acceptable times and exit conditions before the trial. Simulate failures only in the prepared environment; do not interrupt production connections or change production permissions.
Where a manual assistant helps and where software is needed
You can ask an assistant: “Using this fictional P-208 data, separate starting A, current B and Mario’s proposal. Identify differing fields and the missing decision. Do not choose a date, calculate capacity, assume authorisation or generate a save instruction.” Compare its answer with the worksheet: it may omit or misinterpret information.
This conversation helps prepare a review. It does not protect your application’s saves or connect its records. A connected solution requires checking data, access, write rules, error handling and confirmation. If an existing tool covers the process, assess configuration before development; integration or custom development makes sense when necessary rules remain uncovered and the scope is validated.
What to send Adaris to scope the first delivery
Describe the record your team shares, the two edits that can overlap, which value must not be lost and who decides when they differ. Include the fictional sequence and ask to assess an initial delivery with the checks above, plus agreed documentation, recovery and maintenance. Connections, cost and schedule depend on the case; an existing connector is not assumed.
Before sharing real data, agree authorisation, processing terms, access and an appropriate channel. Commercial contact is in Spanish. Start by describing one overlapping edit: you do not need a complete technical specification to begin the conversation.
Related services
Sources
Which change must your team retain?
Describe overlapping edits using fictional data. We will agree what to evaluate and how to check an initial delivery. Commercial contact is in Spanish.