Insert Or Update Sales Order with Megaventory API

Pipedream makes it easy to connect APIs for Megaventory and 2,400+ other apps remarkably fast.

Trigger workflow on

HTTP requests, schedules and app events

Next, do this

Insert Or Update Sales Order with the Megaventory API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

Create a workflow to Insert Or Update Sales Order with the Megaventory API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the Insert Or Update Sales Order action
1. Connect your Megaventory account
2. Select a Sales Order Type ID
3. Select a Client ID
4. Select a Inventory Location ID
5. Select a Sales Order Status
6. Select a Product SKU
7. Configure Sales Order Row Quantity
8. Optional- Select a Sales Order ID
9. Optional- Configure Sales Order No
Select a trigger to run your workflow on HTTP requests, schedules or app events
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Insert Or Update Sales Order with Megaventory API on New Requests from HTTP / Webhook API

HTTP / Webhook + Megaventory

Try it

Insert Or Update Sales Order with Megaventory API on New Submission from Typeform API

Typeform + Megaventory

Try it

Insert Or Update Sales Order with Megaventory API on New Submission (Instant) from Jotform API

Jotform + Megaventory

Try it

Insert Or Update Sales Order with Megaventory API on New Custom Webhook Events from Stripe API

Stripe + Megaventory

Try it

Insert Or Update Sales Order with Megaventory API on New Scheduled Tasks from Pipedream API

Pipedream + Megaventory

Try it

Details#

This is a pre-built, source-available component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Insert Or Update Sales Order on Megaventory

Description:Insert or update a sales order in the database. [See the docs](https://api.megaventory.com/v2017a/documentation/index.html#!/SalesOrder/postSalesOrderSalesOrderUpdate_post_3).

Version:0.0.1

Key:megaventory-insert-or-update-sales-order

View on GitHub

Code#

import app from "../../megaventory.app.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "megaventory-insert-or-update-sales-order",
  name: "Insert Or Update Sales Order",
  description: "Insert or update a sales order in the database. [See the docs](https://api.megaventory.com/v2017a/documentation/index.html#!/SalesOrder/postSalesOrderSalesOrderUpdate_post_3).",
  type: "action",
  version: "0.0.1",
  props: {
    app,
    salesOrderTypeId: {
      label: "Sales Order Type ID",
      description: "The ID of the sales order type.",
      propDefinition: [
        app,
        "documentTypeId",
        () => ({
          args: {
            data: {
              Filters: [
                {
                  FieldName: "DocumentTypeDescription",
                  SearchOperator: "Equals",
                  SearchValue: "Sales Order",
                },
              ],
            },
          },
        }),
      ],
    },
    salesOrderClientId: {
      label: "Client ID",
      description: "The ID of the client.",
      propDefinition: [
        app,
        "supplierClientId",
        () => ({
          args: {
            data: {
              Filters: [
                {
                  FieldName: "SupplierClientType",
                  SearchOperator: "Equals",
                  SearchValue: "Client",
                },
              ],
            },
          },
        }),
      ],
    },
    salesOrderInventoryLocationId: {
      propDefinition: [
        app,
        "inventoryLocationId",
      ],
    },
    salesOrderStatus: {
      type: "string",
      label: "Sales Order Status",
      description: "The status of the sales order.",
      options: Object.values(constants.SALES_ORDER_STATUS),
    },
    productSKU: {
      type: "string",
      label: "Product SKU",
      description: "The SKU of the product.",
      propDefinition: [
        app,
        "product",
        () => ({
          mapper: ({
            ProductSKU: value, ProductDescription: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    salesOrderRowQuantity: {
      type: "integer",
      label: "Sales Order Row Quantity",
      description: "The quantity of the product.",
    },
    salesOrderId: {
      optional: true,
      propDefinition: [
        app,
        "salesOrderId",
      ],
    },
    salesOrderNo: {
      type: "string",
      label: "Sales Order No",
      description: "The sales order number.",
      optional: true,
    },
  },
  methods: {
    insertOrUpdateSalesOrder({
      data, ...args
    } = {}) {
      return this.app.post({
        path: "/SalesOrder/SalesOrderUpdate",
        data: {
          mvRecordAction: constants.MV_RECORD_ACTION.INSERT_OR_UPDATE_NON_EMPTY_FIELDS,
          ...data,
        },
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      salesOrderTypeId,
      salesOrderClientId,
      salesOrderInventoryLocationId,
      salesOrderStatus,
      productSKU,
      salesOrderRowQuantity,
      salesOrderId,
      salesOrderNo,
    } = this;

    const response = await this.insertOrUpdateSalesOrder({
      data: {
        mvSalesOrder: {
          SalesOrderTypeId: salesOrderTypeId,
          SalesOrderClientID: salesOrderClientId,
          SalesOrderInventoryLocationID: salesOrderInventoryLocationId,
          SalesOrderStatus: salesOrderStatus,
          SalesOrderDetails: [
            {
              SalesOrderRowProductSKU: productSKU,
              SalesOrderRowQuantity: salesOrderRowQuantity,
            },
          ],
          SalesOrderId: salesOrderId,
          SalesOrderNo: salesOrderNo,
        },
      },
    });

    step.export("$summary", `Successfully inserted or updated sales order with ID ${response.mvSalesOrder.SalesOrderId}.`);

    return response;
  },
};

Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Megaventory	`app`	`app`	This component uses the Megaventory app.
Sales Order Type ID	`salesOrderTypeId`	`integer`	Select a value from the drop down menu.
Client ID	`salesOrderClientId`	`integer`	Select a value from the drop down menu.
Inventory Location ID	`salesOrderInventoryLocationId`	`integer`	Select a value from the drop down menu.
Sales Order Status	`salesOrderStatus`	`string`	Select a value from the drop down menu:`{ "label": "Pending", "value": "Pending" }{ "label": "Verified", "value": "Verified" }{ "label": "Closed", "value": "Closed" }{ "label": "Cancelled", "value": "Cancelled" }{ "label": "ReOpened", "value": "ReOpened" }{ "label": "Shipped", "value": "Shipped" }`
Product SKU	`productSKU`	`string`	Select a value from the drop down menu.
Sales Order Row Quantity	`salesOrderRowQuantity`	`integer`	The quantity of the product.
Sales Order ID	`salesOrderId`	`integer`	Select a value from the drop down menu.
Sales Order No	`salesOrderNo`	`string`	The sales order number.

Authentication#

Megaventory uses API keys for authentication. When you connect your Megaventory account, Pipedream securely stores the keys so you can easily authenticate to Megaventory APIs in both code and no-code steps.

You can generate an API key for each user of your Megaventory account from Admin -> Users -> Display all -> Click on the user name. You can also copy-paste this link -https://[YOURDOMAIN].megaventory.com/inventory/default.aspx?data=editUser&id=[YOURID]&name=[YOURNAME]

Important: Megaventory user access permissions do apply, i.e. each API key carries the permissions of the user who created it.