Which criteria are required for a field to be available for Mass Update? (Choose two.)
Which criteria are required for a field to be available for Mass Update? (Choose two.)
For a field to be available for Mass Update, it must meet two main criteria. Firstly, the field must be displayed on the preferred form for the record type being updated. This ensures that the field is visible and accessible for the updating process. Secondly, the field must support inline editing, which means it should be configurable directly from the list view without needing to open the record. These conditions ensure that the field is both accessible and editable in bulk operations.
The correct answers are C and D. https://suiteanswers.custhelp.com/app/answers/detail/a_id/8419/loc/en_US
The correct answers are C and D. https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N666653.html To be available for mass update, a field must meet the following criteria: It must support inline editing. For more information, see Using Inline Editing. It must be displayed on your preferred form for the record type being updated. If it is a standard field, it must be outside of subtab lists and must not have dependencies on other fields. If it is a custom field, it must be stored and must not have a sourcing relationship.
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N666653.html#Mass-Changes-or-Updates
https://suiteanswers.custhelp.com/app/answers/detail/a_id/8419/loc/en_US To be available for mass update, a field must meet the following criteria: It must support inline editing. It must be displayed on your preferred form for the record type being updated. If it is a standard field, it must be outside of subtab lists and must not have dependencies on other fields. If it is a custom field, it must be stored and must not have a sourcing relationship.
Fields exposed for mass updates are the same as those available for inline editing and include the following: standard fields that are outside of subtab lists and do not have dependencies on other fields, and custom fields that are stored and do not have sourcing relationships.