Skip to content

Fast chronological account timeline with correct dates - #59

Draft
Skyline-Ornella wants to merge 6 commits into
mainfrom
Fast-chronological-customer-timeline-with-correct-dates
Draft

Fast chronological account timeline with correct dates#59
Skyline-Ornella wants to merge 6 commits into
mainfrom
Fast-chronological-customer-timeline-with-correct-dates

Conversation

@Skyline-Ornella

@Skyline-Ornella Skyline-Ornella commented Jul 15, 2026

Copy link
Copy Markdown

Collaboration task


Task related:

  • dateTo filter has today's date by default
  • Activities are sorted chronologically. Each activity type stores its date in a different field, so this picks the best available one:
    • Escalations: slc_startdate, falling back to createdon
    • Leads / Opportunities / Support: createdon
    • Activities (phone calls, appointments, emails): scheduledstart, with fallbacks to scheduledend, actualend, and createdon.
    • Notes (annotations): createdon

NOTE: 2 hours offset is a misconfiguration of user settings and not something to fix in code. The user should select the correct time zone:
ref: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/organization-administration/date-time-zones#time-zones

Settings -> Personalization Settings -> General-tab -> set time zone you are in.

image

Other:

  • Add better account validation for opportunities, leads, and support views: search-button disabled and hint-text is more prominent when no account is selected for these browsing views.

@Skyline-Ornella Skyline-Ornella changed the title Initialize the dateTo filter with today's date by default Fast chronological account timeline with correct dates Jul 15, 2026
…across entities

Replace createdon-only date filtering with note-date aware filtering across entities. The query builder now generates coalesced date clauses using the same field priority as `noteDate` (including escalation and activity-specific fields), applies createdon-only filters where appropriate, and adds a final in-memory date-range check before sorting to keep mixed-result searches consistent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant