API

Product APIs

GET product/structure-versions/{productStructureVersionId}

Details for provided product structure version

HTTP method GET
URI https://api.rambase.net/product/structure-versions/{productStructureVersionId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {productStructureVersionId} Product structure identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 3856, version 8

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
1

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.
$expand String, optional Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable field names. See the Expand and Select page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<ProductStructureVersion>
2
     <ProductStructureVersionId
ProductStructureVersionId

Product structure identifier

>
{Integer}</ProductStructureVersionId>
3
     <Status
Status

Status of product structure

Possible domain values can be found here

>
{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <Name
Name

Name of the product structure version

>
{String}</Name>
6
     <Description
Description

Description of this product structure version

>
{String}</Description>
7
     <Version
Version

Version number of this product structure

>
{Integer}</Version>
8
     <NoteToOperators
NoteToOperators

Information about product structure's version left for production operator

>
{String}</NoteToOperators>
9
     <Revision
Revision

The revision will typically be a major change, as opposed to minor changes stored in the version of the product structure.

>
{String}</Revision>
10
     <ContainsMaterialPendingExpiration
ContainsMaterialPendingExpiration

Flag to indicate if the structure contains products which is at end of life

>
{Boolean}</ContainsMaterialPendingExpiration>
11
     <NeedsMaterialReplacementToRelease
NeedsMaterialReplacementToRelease

A flag to indicate if product structure contains “dummy” product which needs to be replaced in the production work order structure before releasing the production

>
{Boolean}</NeedsMaterialReplacementToRelease>
12
     <IsBaseStructure
IsBaseStructure

If true the structure version is a base structure for product

>
{Boolean}</IsBaseStructure>
13
     <BaseVersion>
14
          <ProductStructureVersionId
ProductStructureVersionId

Product structure identifier

>
{Integer}</ProductStructureVersionId>
15
          <Version
Version

Base version of the product structure. Will initially be set as the version from the products active product structure.

>
{Integer}</Version>
16
          <ProductStructureVersionLink
ProductStructureVersionLink

Product structure reference

>
{String}</ProductStructureVersionLink>
17
     </BaseVersion>
18
     <CreatedBy
CreatedBy

The employee who made this product structure version

>
19
          <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
20
          <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
21
     </CreatedBy>
22
     <Validity>
23
          <EffectiveDate
EffectiveDate

Effective date this product structure will be valid frmo

>
{Date}</EffectiveDate>
24
          <ExpireDate
ExpireDate

Expire date of this product structure

>
{Date}</ExpireDate>
25
     </Validity>
26
     <Drawing
Drawing

Drawing of the product structure

>
27
          <Database
Database

Database of the object

>
{String}</Database>
28
          <FileVersionId
FileVersionId

File identifier

>
{String}</FileVersionId>
29
          <FileName
FileName

Filename to display for the file version. Will be used when downloading the file.

This field is greyed out because it is an expandable field. You have to add $expand=Drawing.FileName in your request URI to get this field

>
{String}</FileName>
30
          <FileExtension
FileExtension

Extension of the file (ex. jpg)

>
{String}</FileExtension>
31
          <DocumentReference
DocumentReference

This field is a freetext field that is maintained by user input and is intended to reflect the file contents identification reference for better document recognition purposes.

>
{String}</DocumentReference>
32
          <InternalFilename
InternalFilename

The internal filename is created automatically based on the ruleset defined for the FileType. The ruleset consists of text and data macros that are combined to create an internal filename when a file is first uploaded. Data macros are only included in the filename if the connected file object matches the object types specified in the filetype ruleset.

>
{String}</InternalFilename>
33
          <FileVersionLink
FileVersionLink

File reference

>
{String}</FileVersionLink>
34
     </Drawing>
35
     <ActivatedBy
ActivatedBy

Employee who activated the product structure

>
36
          <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
37
          <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
38
     </ActivatedBy>
39
     <ProductStructure>
40
          <ProductStructureId
ProductStructureId

Product structure identifier

>
{Long}</ProductStructureId>
41
          <OwnerType
OwnerType

Type of product structure

Possible domain values can be found here

>
{String}</OwnerType>
42
          <Product
Product

The product this structure is valid for

>
43
               <ProductId
ProductId

Product identifier

>
{Integer}</ProductId>
44
               <Status
Status

Status of the product

Possible domain values can be found here

>
{Integer}</Status>
45
               <Name
Name

Name of the product

>
{String}</Name>
46
               <Type
Type

Type of product

Possible domain values can be found here

>
{String}</Type>
47
               <Description
Description

Description of the product

>
{String}</Description>
48
               <ProductLink
ProductLink

Product identifier

>
{String}</ProductLink>
49
          </Product>
50
          <Owner
Owner

The owner of the product structure

>
51
               <ObjectId
ObjectId

Identifier of the object

>
{Integer}</ObjectId>
52
               <ObjectType
ObjectType

Type of object

>
{String}</ObjectType>
53
               <ObjectLink
ObjectLink

API reference to the object

>
{String}</ObjectLink>
54
               <ItemId
ItemId

Item-number of the object

>
{Integer}</ItemId>
55
               <ItemType
ItemType

Type of item

>
{String}</ItemType>
56
               <ItemLink
ItemLink

API reference to the item

>
{String}</ItemLink>
57
               <RamBaseKey
RamBaseKey

Internal RamBase identifier of the object/item

>
{String}</RamBaseKey>
58
          </Owner>
59
     </ProductStructure>
60
</ProductStructureVersion>
1
{
2
     "productStructureVersion": {
3
          "productStructureVersionId
ProductStructureVersionId

Product structure identifier

":
"{Integer}",
4
          "status
Status

Status of product structure

Possible domain values can be found here

":
"{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "name
Name

Name of the product structure version

":
"{String}",
7
          "description
Description

Description of this product structure version

":
"{String}",
8
          "version
Version

Version number of this product structure

":
"{Integer}",
9
          "noteToOperators
NoteToOperators

Information about product structure's version left for production operator

":
"{String}",
10
          "revision
Revision

The revision will typically be a major change, as opposed to minor changes stored in the version of the product structure.

":
"{String}",
11
          "containsMaterialPendingExpiration
ContainsMaterialPendingExpiration

Flag to indicate if the structure contains products which is at end of life

":
"{Boolean}",
12
          "needsMaterialReplacementToRelease
NeedsMaterialReplacementToRelease

A flag to indicate if product structure contains “dummy” product which needs to be replaced in the production work order structure before releasing the production

":
"{Boolean}",
13
          "isBaseStructure
IsBaseStructure

If true the structure version is a base structure for product

":
"{Boolean}",
14
          "baseVersion": {
15
               "productStructureVersionId
ProductStructureVersionId

Product structure identifier

":
"{Integer}",
16
               "version
Version

Base version of the product structure. Will initially be set as the version from the products active product structure.

":
"{Integer}",
17
               "productStructureVersionLink
ProductStructureVersionLink

Product structure reference

":
"{String}"
18
          },
19
          "createdBy
CreatedBy

The employee who made this product structure version

":
{
20
               "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
21
               "employeeLink
EmployeeLink

Employee reference

":
"{String}"
22
          },
23
          "validity": {
24
               "effectiveDate
EffectiveDate

Effective date this product structure will be valid frmo

":
"{Date}",
25
               "expireDate
ExpireDate

Expire date of this product structure

":
"{Date}"
26
          },
27
          "drawing
Drawing

Drawing of the product structure

":
{
28
               "database
Database

Database of the object

":
"{String}",
29
               "fileVersionId
FileVersionId

File identifier

":
"{String}",
30
               "fileName
FileName

Filename to display for the file version. Will be used when downloading the file.

This field is greyed out because it is an expandable field. You have to add $expand=Drawing.FileName in your request URI to get this field

":
"{String}",
31
               "fileExtension
FileExtension

Extension of the file (ex. jpg)

":
"{String}",
32
               "documentReference
DocumentReference

This field is a freetext field that is maintained by user input and is intended to reflect the file contents identification reference for better document recognition purposes.

":
"{String}",
33
               "internalFilename
InternalFilename

The internal filename is created automatically based on the ruleset defined for the FileType. The ruleset consists of text and data macros that are combined to create an internal filename when a file is first uploaded. Data macros are only included in the filename if the connected file object matches the object types specified in the filetype ruleset.

":
"{String}",
34
               "fileVersionLink
FileVersionLink

File reference

":
"{String}"
35
          },
36
          "activatedBy
ActivatedBy

Employee who activated the product structure

":
{
37
               "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
38
               "employeeLink
EmployeeLink

Employee reference

":
"{String}"
39
          },
40
          "productStructure": {
41
               "productStructureId
ProductStructureId

Product structure identifier

":
"{Long}",
42
               "ownerType
OwnerType

Type of product structure

Possible domain values can be found here

":
"{String}",
43
               "product
Product

The product this structure is valid for

":
{
44
                    "productId
ProductId

Product identifier

":
"{Integer}",
45
                    "status
Status

Status of the product

Possible domain values can be found here

":
"{Integer}",
46
                    "name
Name

Name of the product

":
"{String}",
47
                    "type
Type

Type of product

Possible domain values can be found here

":
"{String}",
48
                    "description
Description

Description of the product

":
"{String}",
49
                    "productLink
ProductLink

Product identifier

":
"{String}"
50
               },
51
               "owner
Owner

The owner of the product structure

":
{
52
                    "objectId
ObjectId

Identifier of the object

":
"{Integer}",
53
                    "objectType
ObjectType

Type of object

":
"{String}",
54
                    "objectLink
ObjectLink

API reference to the object

":
"{String}",
55
                    "itemId
ItemId

Item-number of the object

":
"{Integer}",
56
                    "itemType
ItemType

Type of item

":
"{String}",
57
                    "itemLink
ItemLink

API reference to the item

":
"{String}",
58
                    "ramBaseKey
RamBaseKey

Internal RamBase identifier of the object/item

":
"{String}"
59
               }
60
          }
61
     }
62
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 99946 HTTP 400 {0}: Missing mandatory arguments {1}
Error 101746 HTTP 404 Product structure not found. Id: {0}