Is it viable to use SublistType.INLINEEDITOR and manually retrieve the values (like checkbox and quantity fields) using document.querySelectorAll() from the DOM, instead of relying on currentRecord.getSublistValue() — since the values are not committed yet?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** Based on the conversations, it seems that using

SublistType.INLINEEDITOR

and manually retrieving the values using

document.querySelectorAll()

from the DOM is a viable approach, especially when the values are not committed yet and you cannot rely on

currentRecord.getSublistValue()

. In one of the threads, a user was trying to get the values from a custom sublist added in the

beforeLoad

event using

currentRecord.get().getSublistValue()

, but they encountered the

SSS_INVALID_SUBLIST_OPERATION

error. The suggestion was to use the DOM on client scripts for sublists created on the

beforeLoad

event. In another thread, a user was trying to use

N/currentRecord

along with

.getSublistValue()

in

View

mode on a sales order, but they found that

getLineCount

was returning -1 and

selectLine

wasn't available on

currentRecord

. In a third thread, a user was trying to populate inline fields in a sublist (

serverWidget.SublistType.List

) with inline fields (

serverWidget.FieldDisplayType.INLINE

) in a client script using

scriptContext.currentRecord.setCurrentSublistValue

, but it wasn't working. The suggestion was to try using

nlapiSetCurrentLineItemValue

from SuiteScript 1.0, but the user encountered an error. So, while it is possible to use

SublistType.INLINEEDITOR

and manually retrieve the values using

document.querySelectorAll()

from the DOM, it may not always work as expected and you may encounter errors. It's also important to note that this approach may not be suitable for all use cases and it's recommended to test thoroughly before implementing.