pageSales & Receivablesofficial - Microsoftderived - from the source, no model text

Page 8024 "Customer Contracts API"

Subscription Billing · Microsoft.SubscriptionBilling

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 8052 "Customer Subscription Contract" (relates to)Customer Subscription Contract

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Subscription Billing · Microsoft.SubscriptionBilling · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable Customer Subscription Contract
PageType API
ApplicationArea All

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
General systemId Rec.SystemId —
sellToCustomerNo Sell-to Customer No. —
no No. —
billToCustomerNo Bill-to Customer No. —
billToName Bill-to Name —
billToName2 Bill-to Name 2 —
billToAddress Bill-to Address —
billToAddress2 Bill-to Address 2 —
billToCity Bill-to City —
billToContact Bill-to Contact —
yourReference Your Reference —
shipToName Ship-to Name —
shipToName2 Ship-to Name 2 —
shipToAddress Ship-to Address —
shipToAddress2 Ship-to Address 2 —
shipToCity Ship-to City —
shipToContact Ship-to Contact —
paymentTermsCode Payment Terms Code —
shortcutDimension1Code Shortcut Dimension 1 Code —
shortcutDimension2Code Shortcut Dimension 2 Code —
currencyCode Currency Code —
salespersonCode Salesperson Code —
sellToCustomerName Sell-to Customer Name —
sellToCustomerName2 Sell-to Customer Name 2 —
sellToAddress Sell-to Address —
sellToAddress2 Sell-to Address 2 —
sellToCity Sell-to City —
sellToContact Sell-to Contact —
billToPostCode Bill-to Post Code —
billToCounty Bill-to County —
sellToPostCode Sell-to Post Code —
sellToCounty Sell-to County —
sellToCountryRegionCode Sell-to Country/Region Code —
shipToPostCode Ship-to Post Code —
shipToCounty Ship-to County —
shipToCountryRegionCode Ship-to Country/Region Code —
paymentMethodCode Payment Method Code —
noSeries No. Series —
description Description —
sellToContactNo Sell-to Contact No. —
billToContactNo Bill-to Contact No. —
assignedUserID Assigned User ID —
active Active —
contractType Contract Type —
descriptionPreview Description Preview —
withoutContractDeferrals obsolete Pending 27.0; #if not CLEAN27 Without Contract Deferrals —
createContractDeferrals Create Contract Deferrals —
detailOverview Detail Overview —
billingRhytmFilter Billing Rhythm Filter —
dimensionFromJobNo Dimension from Job No. —
billingBaseDate Billing Base Date —
defaultBillingRhythm Default Billing Rhythm —
nextBillingFrom Next Billing From —
nextBillingTo Next Billing To —
billToCountryRegionCode Bill-to Country/Region Code —
contractorNameInCollInv Contractor Name in coll. Inv. —
dimensionSetID Dimension Set ID —
recipientNameInCollInv Recipient Name in coll. Inv. —
shipToCode Ship-to Code —
customerContractLinesAPI part Page 8045 “Customer Contract Lines API” —

Relations

Recent changes

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Customer Contracts API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources