✅ Real-World Examples: find, exist, checkExist, and txtNotExist Methods in D365FO

 

🔹 1. find Method

x++
client server static CustTable find(AccountNum _accountNum, boolean _forUpdate = false)
{
    CustTable custTable;

    if (_forUpdate)
    {
        custTable.selectForUpdate(_forUpdate);
    }

    select firstonly custTable
        where custTable.AccountNum == _accountNum;

    return custTable;
}

🔸 Purpose: Retrieves a single record based on the unique key (AccountNum).
🔸 Parameter _forUpdate allows the caller to lock the record for update.

---

🔹 2. exist Method

x++
client server static boolean exist(AccountNum _accountNum)
{
    return CustTable::find(_accountNum).RecId != 0;
}

🔸 Purpose: Returns true if the record exists, otherwise false.

---

🔹 3. checkExist Method

x++
client server static void checkExist(AccountNum _accountNum)
{
    if (!CustTable::exist(_accountNum))
    {
        throw error(strFmt("Customer account '%1' does not exist.", _accountNum));
    }
}

🔸 Purpose: Throws an error if the record is not found. Useful for validations in business logic.

---

🔹 4. txtNotExist Method

x++
client server static str txtNotExist(AccountNum _accountNum)
{
    if (!CustTable::exist(_accountNum))
    {
        return strFmt("Customer '%1' not found in the system.", _accountNum);
    }

    return "";
}

🔸 Purpose: Returns a user-friendly message when the record doesn’t exist. Useful for logging or notifications.

---

🧠 Why Use These Methods?

• ✅ Centralizes logic

• ✅ Reduces code duplication

• ✅ Improves readability

• ✅ Follows Microsoft-recommended design patterns

---

💡 Pro Tip

You can also override these methods in your own custom tables (like MySalesContractTable) following the same pattern—just replace the key field and table name accordingly.