Skip to content

[BC Idea]: "Subscription Period: XX to ZZ" in sales document generated from Subscription Billing app should be configurable (the text) #5255

Description

@TKapitan

BC Idea Link

https://experience.dynamics.com/ideas/idea/?ideaid=2fa5df52-8eae-f011-aa43-6045bdaf6902

Description

"Subscription Period: XX to ZZ" in sales document generated from Subscription Billing app should be configurable (the text)

I've seen this requirement multiple times as for many customers "Subscription Period" is not what they want - it could be "Billing Period" or "Rental Period" depending on the business requirements

I will provide the implementation for this BC Idea

  • I will provide the implementation for this BC Idea
    Internal work item: AB#612913

Activity

  1. pri-kise commented on Oct 22, 2025

    @pri-kise
    Contributor

    Please also think of multi language version for the label. (maybe via the table tranlsation)

  2. added
    ADO: SyncCreates an Azure DevOps work item if needed and indicates that one is linked
    on Nov 14, 2025
  3. AndersLarsenMicrosoft commented on Aug 20, 2026

    @AndersLarsenMicrosoft
    Contributor

    Is this still needed then reactivate and provide the PR

  4. pri-kise commented on Aug 22, 2026

    @pri-kise
    Contributor

    Thanks — I'd like to pick this up. Could you please reopen the issue?

    Here's the approach I'm proposing (and have implemented in a branch / draft pull request):

    Add a configurable Billing Period Description field (Text[50]) on the Subscription Contract Type rather than a single global setting, so different contract types can use different wording (e.g. "Billing period", "Subscription period", "Rental period"). The field keeps the %1 / %2 placeholders for the period start/end dates.
    Multi-language is handled via the existing Field Translation pattern already used for the contract type Description. The Contract Types page gets the field, a translations-count control with drill-down, and a promoted "Billing Period Translations" action.

    At billing time the text is resolved from the contract's type → language translation → standard label, for both sales and purchase documents.
    Backward compatible: leaving the field blank keeps today's standard text, so existing setups are unaffected and no upgrade is required.
    Includes unit tests for the sales/purchase custom text, the translated variant, and translation cleanup on delete/clear.

    Does this design look good to you? If so, please reopen and I'll publish the PR

  5. JesperSchulz commented on Oct 1, 2026

    @JesperSchulz
    Contributor

    🤖 AI triage completed. Product group, please validate the triage report (Microsoft internal access only, use Ctrl+Click to open in new tab).


    Was this triage helpful? React with 👍 or 👎 on this comment to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ADO: SyncCreates an Azure DevOps work item if needed and indicates that one is linkedApprovedThe issue is approvedBCIdeaIssue related to a BCIdeaLinkedTeam: FinanceGitHub request for Finance area

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions