Page 30151 "Shpfy Return"

Shopify · Microsoft.Integration.Shopify · captioned “Shopify Return” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Shopify Return
SourceTable	Shpfy Return Header
PageType	Document
UsageCategory	None
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	Return No.	Return No.	Specifies the No. of the return.
	Shopify Order No.	Shopify Order No.	Specifies the unique identifier for the order that appears on the order page in the Shopify admin and the order status page. For example, “#1001”, “EN1001”, or “1001-A”.
	Status	Status	Specifies the status of the return.
	Sell-to Customer No.	Sell-to Customer No.	Specifies the value of the Sell-to Customer No. field.
	Sell-to Customer Name	Sell-to Customer Name	Specifies the value of the Sell-to Customer Name field.
	Bill-to Customer No.	Bill-to Customer No.	Specifies the value of the Bill-to Customer No. field.
	Bill-to Customer Name	Bill-to Customer Name	Specifies the value of the Bill-to Customer Name field.
	Decline Reason	Decline Reason	Specifies the reason the customer’s return request was declined.
	Total Quantity	Total Quantity	Specifies the sum of all line item quantities for the return.
Content	Lines	part Page 30149 “Shpfy Return Lines”	—
Decline Note	Decline Note	`Rec.GetDeclineNote()`	Specifies the sum of all line item quantities for the return.

Actions

Group	Action	ToolTip	Runs
Processing	Retrieved Shopify Data	View the data retrieved from Shopify.

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord, OnAfterGetRecord

Relations

source table Table 30147 “Shpfy Return Header”

Pages and codeunits on this table

Page 30150 “Shpfy Returns” (card page)

Documented on Microsoft Learn

Synchronize and fulfill sales orders

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "Shpfy Return"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 3 connected objects and pages