BC Friday Tips #69 Item Blocked Fields

Key points

• Item table contains multiple separate blocked fields for different modules
• Checking only the generic Blocked field can allow restricted actions like sales on sales-blocked items
• Item Variant and other tables also have multiple blocked fields
• Developers should validate against all relevant blocked fields based on context
• Ignoring module-specific fields creates bugs that only appear in certain scenarios

Quotes

• “If your code only checks the Blocked field, your logic can break.” (Highlights the critical risk of incomplete validation that leads to unintended behavior)
• “You may allow actions that should be restricted, such as sales on items that are blocked for sales.” (Demonstrates the specific consequence of ignoring module-specific blocked fields)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

• table 27 “Item”
• table 5401 “Item Variant”

Context

• Features: Item blocking, Sales blocking, Purchasing blocking, Service blocking

Source: That NAV Guy, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.