Decide where the work belongs
Identify the changed date meaning
Compare known source dates with imported results and one affected workflow. Record swapped day/month values, serial interpretation errors, and display-only differences separately. Keep calendar dates distinct from timestamps, because an apparent one-day difference may involve a later timezone boundary rather than the same source-format defect.
Group by producer representation
Identify exports containing serial values, explicit date strings, or ambiguous localized text. Compare the documented support and observed outcomes for each. Estimate exposure from those actual representations rather than all spreadsheet imports or a user’s locale, which may differ from the settings used to create the source export.
Assess correction confidence
Check whether preview exposes the interpreted date and offers an appropriate supported format choice. Determine whether already imported values can be reconciled with known source context. A blanket offset or day/month swap is not a reliable workaround when the affected population includes several different representations or ambiguous dates.
What to carry forward
Record priority with confirmed date changes, workflow consequences, producer reach, and reconciliation confidence. Assign a trigger for silently accepted wrong dates or a new export convention. Keep unsupported formats and missing source context explicit instead of promising an automatic repair that cannot uniquely recover the intended calendar value.
Technical background: Microsoft support.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow