API Input Builder Factory

EnviousMothman avatar
EnviousMothman
·
·
Download

Start Quiz

Study Flashcards

15 Questions

What is the purpose of api.inputBuilderFactory()?

To create a new input builder factory.

When api.inputBuilderFactory() is executed alone, what does it return?

New input builder factory instance

What is the use of getInput() and how does it work?

The getInput() method is used to retrieve input data from the server.

In what format is the input created in the server?

The input is created in the server in a specified format.

What is the type of userentry()?

The type of userentry() is unspecified.

What are different types of calculation context?

Init, Row, and Calculation

For what calendar data type is used?

Handling data related to specific time frames or dates

What is model calculation type?

It is a method of defining and processing calculations within a data model context

What is publishing data type?

It involves making data accessible to a wider audience or specific users for consumption

Simulation data type is used for?

Evaluating hypothetical situations or scenarios without affecting actual data

What are the data loads that will be automatically created and when?

Init, Row, Calculation, Publishing, and Simulation data loads

What are the various types of status and what each one of them means?

Includes statuses like Draft, Completed, In Progress, Error, etc.

Can we able to modify the target in automatically generated data load?

Yes, in some cases based on the specific requirements

When the source will be selected in the data load?

Before the data loading process is initiated

Do load date influence the updation of the data?

Yes, the load date can impact how the data is updated or processed

Study Notes

API

api.inputBuilderFactory()

  • Returns a builder for creating inputs.
  • Purpose: to create inputs.

api.isDebugMode()

  • Purpose: to check if the system is in debug mode.
  • Usage: to enable debug mode during development.

api.isAbortCalculation()

  • Purpose: to abort calculation.
  • Usage: to stop calculation when a condition is met.
  • Returns: a boolean value indicating if the calculation is aborted.

api.find()

  • Purpose: to find data.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve data from tables.
  • Limitations: returns a limited number of records.
  • Overload: exists with different parameters.

api.stream()

  • Purpose: to stream data.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve large amounts of data.
  • Limitations: returns a stream of data.
  • Differences: from api.find().

api.product()

  • Purpose: to retrieve products.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve products.
  • Differences: from api.find().

api.customer()

  • Purpose: to retrieve customers.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve customers.
  • Differences: from api.find().

api.productextension()

  • Purpose: to retrieve product extensions.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve product extensions.
  • Differences: from api.find().

api.customerextension()

  • Purpose: to retrieve customer extensions.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve customer extensions.
  • Differences: from api.find().

api.vLookup()

  • Purpose: to retrieve data from lookup tables.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve data from lookup tables.
  • Differences: from api.find().

api.findLookupTable()

  • Purpose: to retrieve lookup tables.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve lookup tables.
  • Differences: from api.find().

api.findLookupTableValues()

  • Purpose: to retrieve lookup table values.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve lookup table values.
  • Differences: from api.find().

api.getDatamartContext()

  • Purpose: to get the datamart context.
  • Usage: to access the datamart context.
  • Returns: the datamart context.

api.getDatamartContext().getDataMart()

  • Purpose: to get the data mart.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve the data mart.
  • Returns: the data mart.

api.getDatamartContext().getDataSource()

  • Purpose: to get the data source.
  • Parameters: multiple parameters can be passed.
  • Usage: to retrieve the data source.
  • Returns: the data source.

api.getDatamartContext().newQuery()

  • Purpose: to create a new query.
  • Parameters: multiple parameters can be passed.
  • Usage: to create a new query.
  • Returns: the new query.

api.getDatamartContext().executeQuery()

  • Purpose: to execute a query.
  • Parameters: multiple parameters can be passed.
  • Usage: to execute a query.
  • Returns: the result of the query.

Master Data

  • Master data is stored in a database.
  • Purpose: to store master data.
  • Types: Company, Product, Customer, and Price Parameter tables.

Analytics

  • Purpose: to analyze data.
  • Usage: to create queries, aggregate data, and filter data.
  • Functions: select, selectAll, orderby, groupby, having, where, and setOptions.

DataSource

  • Purpose: to define a data source.
  • Usage: to configure a data source.
  • Functions: templates, key, Alt-key, Level, and data type.

DataFeed

  • Purpose: to define a data feed.
  • Usage: to configure a data feed.
  • Differences: from DataSource.

Datamart

  • Purpose: to define a datamart.
  • Usage: to configure a datamart.
  • Functions: fields, measures, and expressions.

DataLoad

  • Purpose: to load data.
  • Usage: to configure a data load.
  • Types: internal copy, products, customers, and calculating context.

Dashboard

  • Purpose: to create a dashboard.
  • Usage: to configure a dashboard.
  • Functions: dynamic inputs, hide, and category.

PriceList

  • Purpose: to define a price list.
  • Usage: to configure a price list.
  • Functions: price setting, matrix logic, and dynamic UOM.

Workflow

  • Purpose: to define a workflow.
  • Usage: to configure a workflow.
  • Types: pricelist, quote, and LPG.

Quotes

  • Purpose: to define a quote.
  • Usage: to configure a quote.
  • Functions: quote header, quote line item, and workflow.

Error Handling and Exception

  • Purpose: to handle errors and exceptions.
  • Usage: to catch and handle errors.
  • Types: arithmetic, null, and custom exceptions.

Workflow

  • Purpose: to define a workflow.
  • Usage: to configure a workflow.
  • Functions: steps, approvers, and reasons.

Quiz about the purpose and usage of api.inputBuilderFactory() and related methods.

Make Your Own Quizzes and Flashcards

Convert your notes into interactive study material.

Get started for free

More Quizzes Like This

Django API Development Quiz
29 questions
What is API?
10 questions

What is API?

WellRegardedParadox avatar
WellRegardedParadox
Use Quizgecko on...
Browser
Browser