web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Make the bank account mandatory while creating a new vendor

(0) ShareShare
ReportReport
Posted on by 546

Hi Good Community,

I have a requirement to force the user to enter a new bank account record and make it mandatory for completing the vendor creation process the problem is the bank account is a child table related to the vendor table, how to force the end user for the creation otherwise skipping the vendor creation.

pastedimage1671384849368v1.png

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    303,679 Super User 2026 Season 1 on at

    Hi Ahmed,

    As the vendor record should exist before you can open the bank accounts form, it is not possible to achieve your requirement without a customization or ISV solution.

    You can consider developing a creation dialog form having information from both the vendor and the bank account. Then you can add validations before writing any data to the actual tables.

    Note that we, at To-Increase, have an ISV solution called Data Entry Workflow where you can configure data entry for master and reference data with one or more steps which can be assigned to different users. You can not only configure to collect data from e.g. the vendor and bank account details, but also ensure that there will be an approval step before the data becomes available to end users. To-Increase - MDM - Data Entry Workflow - Product Page

  • ahmed.kimo Profile Picture
    546 on at

    Hi André,

    That is great actually .

    But do we have any opportunity to save the vendor record in the buffer without saving in the DB then commit the changes before leaving the form at once , or any option to skip the created record if the user leave the form without filling the information related to the bank account

  • André Arnaud de Calavon Profile Picture
    303,679 Super User 2026 Season 1 on at

    Hi Ahmed,

    If you develop something yourself, you can control with x++ coding when data will be written or not. You can add validations e.g. on validateWrite() and then ensure both records will be written at the same time.

    You can't save a vendor record without saving it in the database, or you should think of a separate staging table. In our Data Entry Workflow solution, we store all values for all fields in a staging environment and only when all information is complete it will create the records in the actual tables.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 617

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 461 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 298 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans