A few of our REST API endpoints can be used with both Portal 2.0 and Portal 3.0 to provide a bridge between both versions of Portal and provide a similar experience when importing to each version of our Portal product. However, since Portal 2.0 and Portal 3.0 are built differently, there are a few fields that are only relevant for one or the other. The
countColumns fields are examples of fields that only return values for Portal 2.0. This means when importing to Portal 3.0, you will see "null" values returned for these.
To retrieve your row counts for imports to Portal 3.0, we recommend using the
getRowsFromEmbedBatch GraphQL query. This query will take your
batchId and a
filter, which can be "valid", "invalid", or "merged". If you don't use the filter argument, the records will be returned in a different format with a validations object on each row that will display an array of any present errors or warnings.