...
Type Code | Description |
---|---|
P | Product Master |
PX | Product Extension (see Searching in Product Extensions) |
C | Customer Master |
CX | Customer Extension |
PL | Price List |
PLI | Price List Item |
MPL | Manual Price List |
MPLI | Manual Price List Item |
PG | Live Price Grid |
PGI | Live Price Grid Item |
CA | Customer Assignments |
Q | Quote |
...
For searching in Price Parameters, you should almost exclusively use specialized methods api.findLookupTable
and api.findLookupTableValues
. For more details see Searching in Price Parameters.
Using Attribute Names in Searches
...
- The number of rows the method api.find can return is limited by a server parameter. It is configurable per partition and by default it is set to 200. You can retrieve the max rows by calling api.getMaxFindResultsLimit. Read how to overcome this limitation below.
A warning is displayed if the number of returned rows returned equals 200 or formulaEngine.script.findMaxResults and the maxRows parameter of the find was not specified (=0). - When filtering the attributed fields (attribute1, ..., attribute30), you need to pass strings to filters because all attributed fields are stored in the database as strings. This is mainly an issue with Dates. Find out how to convert them properly.
- Because of the previous point, you cannot use sorting on numbers (integers, real) because api.find returns and sorts the data as strings. When sorting ($100, $70, $25) ascending, the result will be ($100, $25, $70).
- Using
api.find
/api.stream
it is not possible to retrieve thetypedId
field. These methods produce a DB query and in the DB we store an "id" field. So, to gettypedId
you would have to manually concatenate the "id" and "type" fields with a dot in a postprocessing logic.
...