Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Journal Transaction No...
Microsoft Dynamics SL (Archived)

Journal Transaction Non Post Project

(0) ShareShare
ReportReport
Posted on by Candice82 2

I need to be able to create a journal transaction using the non post project that was set up in project controller and fill out the employee id field.

I have opened COA and set an account category that needs to be used with the account. I also checked the "require employee" box. After filling out the account, it allows me to use the non post project account; however, it does not allow me to enter anything in the employee field. If I choose any other project, I can fill out the employee id field. Is it possible to do what I'm asking? 

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Journal Transaction Non Post Project

    No it would still post to that dummy project.  You would just ignore that project, filtering it out of any project reports.

  • Candice82 Profile Picture
    Candice82 2 on at
    RE: Journal Transaction Non Post Project

    So, you're saying there's no way to do it out of the box, without tricking the system? If a dummy project was used, is there a way to make it not post against it?

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Journal Transaction Non Post Project

    When you enter the non-post project into the project field the employee Id field is disabled.  

    So you basically have to trick the system.  

    Insert a new field on the screen in the grid area.  Use a user character field from the GLTran like User1.

    Move the regular employee field off to the side and mark it as invisible and disabled.

    Place the new field where the regular employee field was. Give it a tab index right after the regular employee field.  Also copy the PV and the Mask from the regular employeeID field into the new field properties.

    Then in the chk Event of the new field use the SetBufferValue to set the original employee ID field equal to the chk string.  I.E.:

    Call SetBufferValue("bgltran.employeeid", ChkStrg)

    You could also use an unbound control to instead of a user field but that means that you will have to write some code to display the employee ID from existing records in that unbound control.

    You probably will also need to write some code to set the employee field as disabled when you are using a non-project account and required when the account says that employee is required.  In other words you should duplicate what the underlying code does with the original employee ID field except make it enabled when you use the non-post project.

    You also could just set up a dummy project to handle this instead of using the non-post.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,468 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,287 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans