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

Notifications

Announcements

No record found.

Community site session details

Community site session details

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

Error No assembly matching referenced module 'PublicSectorFormAdaptor' is found

(0) ShareShare
ReportReport
Posted on by 576

Hello..

First I open D VS as admin then create new project named with new model , in select reference packages I select all packages

, then create RunnableClass named rename

class RunnableClass1
{        
    /// 
    /// Runs the class with the specified arguments.
    /// 
    /// The specified arguments.
    public static void main(Args _args)
    {   
        VendTable     VendTable;

        select firstonly VendTable where VendTable.AccountNum == "1001";
        VendTable.AccountNum = "11001";
        VendTable.renamePrimaryKey();
    }

}

when pressed start button , it gave me an error


Error No assembly matching referenced module 'PublicSectorFormAdaptor' is found. 0

Any help ?
 

I have the same question (0)
  • Verified answer
    nmaenpaa Profile Picture
    101,160 Moderator on at

    Don't reference the form adaptor packages. You should only reference the packages that you need.

    FormAdaptor packages are available only in dev systems, not in test/prod so you should never have dependency in them.

  • Verified answer
    Blue Wang Profile Picture
    on at

    Hi Ahmed,

    Why do you need to reference PublicSectorFormAdaptor?

    Just remove it. The same is true of the environment I use for testing.

    Don't add PublicSectorFormAdaptor model in your package neither your custom model create reference from PublicSectorFormAdaptor model, because PublicSectorFormAdaptor model is not present in on-premises environment.

    More details, please read this blog:

    exploringd365.blogspot.com/.../d365-on-premise-packages-exclude-models.html

  • Joris dG Profile Picture
    17,775 on at

    Also, please avoid the rename primary key functionality. It's a recipe for problems. If it weren't for the fact it would break a lot of people that actually use it, this feature would have been removed from the product altogether.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

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

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans