-
Notifications
You must be signed in to change notification settings - Fork 318
Enhanced Subscription & Billing demo data for Power BI reporting #6143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Enhanced Subscription & Billing demo data for Power BI reporting #6143
Conversation
New updates to Sub & Billing Demo Data app: - Updated last used no series. - Added subscriptions - Added customer and vendor subscription contracts - Created analysis entries for PowerBI reporting. http://bcdev2.fenwicksoftware.com.au:10470/BC/?company=DemoSB3 Related work items: #29613
| end; | ||
| end; | ||
|
|
||
| local procedure CreateContractAnalysisEntry(ServiceCommitment: Record "Subscription Line"; AnalysisDate: Date) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| local procedure CreateContractAnalysisEntry(ServiceCommitment: Record "Subscription Line"; AnalysisDate: Date) | |
| local procedure CreateContractAnalysisEntry(SubscriptionLine: Record "Subscription Line"; AnalysisDate: Date) |
I am not familiar with this record so maybe your name makes more sense, but generally we name the record variables exactly like their source table.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@attilatoury I'm not sure why they aren't same here. I followed the same naming convention that's used within this Sub & Billing Demo Data app. And yes, normally it would be the same name as the record in AL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated this changed anyway
|
|
||
| ServiceObject.Validate("End-User Customer No.", CustomerNo); | ||
| ServiceObject.Validate("Provision Start Date", ProvisionStartDate); | ||
| if ProvisionEndDate <> 0D then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we check that StartDate < EndDate? Unless it is already done in the table field's OnValidate trigger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, there is no onvalidate code. I've added this check.
| VendorContract.CreateVendorContractLineFromServiceCommitment(ServiceCommitment); | ||
| end; | ||
|
|
||
| procedure AddVendorContractLine(ContractNo: Code[20]; ObjectNo: Code[20]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call this procedure at the end of the procedure above (InsertVendorContractLine) if it is intended to do the same thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated this change
Summary
Subscription & Billing Demo Data
Work Item(s)
Fixes #6142
Fixes AB#614285