Search Results for

    Show / Hide Table of Contents

    engChangeNotice Resource Type

    Use the "engChangeNotice" API to create and manage Engineering Change Notices (ECNs). From an Approved ECN, you can create an Engineering Change Order (ECO) via an action.

    • API version: v2.0
    • Publisher: cosmoconsult
    • Group: productdatamanagement
    • Base (SaaS): https://api.businesscentral.dynamics.com/v2.0/{tenant}/Production/api/cosmoconsult/productdatamanagement/v2.0
    • Base (On‑Prem): https://{host}/{container}rest/api/cosmoconsult/productdatamanagement/v2.0
    • Metadata: {Base}/$metadata?tenant=default&$schemaversion=2.0

    Permissions

    Requires access to the target company and permissions to read/write ECNs.

    Methods

    Operation Company‑scoped Unscoped
    List ECNs GET /companies({companyId})/engChangeNotices GET /engChangeNotices
    Create ECN POST /companies({companyId})/engChangeNotices POST /engChangeNotices
    Get ECN GET /companies({companyId})/engChangeNotices({id}) GET /engChangeNotices({id})
    Update ECN PATCH /companies({companyId})/engChangeNotices({id}) PATCH /engChangeNotices({id})
    Delete ECN DELETE /companies({companyId})/engChangeNotices({id}) DELETE /engChangeNotices({id})
    Create ECO (action) POST /companies({companyId})/engChangeNotices({id})/Microsoft.NAV.createEngChangeOrder POST /engChangeNotices({id})/Microsoft.NAV.createEngChangeOrder

    Endpoints

    Company‑scoped

    • GET /companies({companyId})/engChangeNotices
    • POST /companies({companyId})/engChangeNotices
    • GET /companies({companyId})/engChangeNotices({id})
    • PATCH /companies({companyId})/engChangeNotices({id})
    • DELETE /companies({companyId})/engChangeNotices({id})
    • POST /companies({companyId})/engChangeNotices({id})/Microsoft.NAV.createEngChangeOrder (action)
    • GET/POST /companies({companyId})/engChangeNotices({id})/engChangeNoticeComments
    • GET/PATCH/DELETE /companies({companyId})/engChangeNotices({id})/engChangeNoticeComments({id1})
    • GET/POST /companies({companyId})/engChangeNotices({id})/engChangeNoticeBOMLines
    • GET/PATCH/DELETE /companies({companyId})/engChangeNotices({id})/engChangeNoticeBOMLines({id1})

    Unscoped

    • GET/POST /engChangeNotices
    • GET/PATCH/DELETE /engChangeNotices({id})
    • POST /engChangeNotices({id})/Microsoft.NAV.createEngChangeOrder (action)
    • GET/POST /engChangeNotices({id})/engChangeNoticeComments
    • GET/PATCH/DELETE /engChangeNotices({id})/engChangeNoticeComments({id1})
    • GET/POST /engChangeNotices({id})/engChangeNoticeBOMLines
    • GET/PATCH/DELETE /engChangeNotices({id})/engChangeNoticeBOMLines({id1})

    Related collections (direct sets)

    • GET/POST /companies({companyId})/engChangeNoticeComments
    • GET/PATCH/DELETE /companies({companyId})/engChangeNoticeComments({id})
    • GET/POST /companies({companyId})/engChangeNoticeBOMLines
    • GET/PATCH/DELETE /companies({companyId})/engChangeNoticeBOMLines({id})

    Notes on runtime behavior

    • ECN must be Approved before calling createEngChangeOrder.
    • BOM Lines: Insert/Delete via API are blocked by the page logic; only updates are supported. If a DELETE/POST endpoint exists in metadata, it will return an error at runtime.

    Query Options

    $select, $filter, $orderby, $expand (engChangeNoticeComments,engChangeNoticeBOMLines), $top, $skip

    Request Headers

    • Authorization: Bearer {token}
    • Content-Type: application/json (POST/PATCH)
    • If-Match: {etag} (required for PATCH; use * only for testing)

    Key Properties (Short)

    • id (SystemId, GUID), number, status
    • itemNumber, itemDescription (read‑only)
    • changeReasonCode, changeReasonDescription (read‑only)
    • drawingNumber, drawingTypeCode
    • sourceType, sourceStatus/sourceSalesDocumentType (where applicable), sourceNumber, sourceSequence
    • bomCommentExists (read‑only), bomExists (read‑only)
    • creationDate, createdBy, lastModifiedDateTime (read‑only)

    Examples

    • List with details: GET {Base}/companies({companyId})/engChangeNotices?$expand=engChangeNoticeComments,engChangeNoticeBOMLines

    • Create (minimal): POST {Base}/companies({companyId})/engChangeNotices Content-Type: application/json { "sourceType": "Prod_x002E__x0020_Order_x0020_Line", "sourceStatus": "Released", "sourceNumber": "101001", "sourceSequence": 10000, "changeReasonCode": "CUSTOMER" }

    • Approve: PATCH {Base}/companies({companyId})/engChangeNotices({id}) If-Match: * { "status": "Approved" }

    • Create ECO: POST {Base}/companies({companyId})/engChangeNotices({id})/Microsoft.NAV.createEngChangeOrder

    See Also

    engChangeOrder
    engChangeNoticeComment
    engChangeNoticeBOMLine


    Feedback
    Senden Sie Feedback für diese Seite . (Beachten Sie, dass diese Umfrage auf Englisch ist.)

    In This Article
    Back to top 2025 © COSMO CONSULT - Data protection - Imprint