A practitioner’s musings on Dynamics 365 Finance and Operations
Lets start the blog, with very simple entry.
In D365 Finance and Operations, We can add customize fields and same time we can add make any field mandatory.
For example we want to set vendor “Duns Number” as mandatory.
For this we
Right click and click on Duns number
From pop menu, select click on
Then click on Personalize this page.
Click on Close
Edit the page and you found * button on DUNS Number.
Edit the button, On pressing the save button you found * option.
See you in next blog post
I was at client side.
End user did not going to sign off the functionality. He wants a few more changes. All these changes are very nice to have features.
In go live situation it is not possible to accommodate these. If end user or key person would not sign off and as result no go live. When project is not go live. Then there will no payment release.
As result we are failure. We can not modify things at 11th hour. Who do the enhancement, who test it. And if we deliver not tested things in front of client. his trust will be broken.
EPR implementation is very slow process. When project kick off and now on go live.
There are many people both our and client side already left. The best way to handle this situation is signed Functional Requirement Document. If things varies from this document. We would not do that. That reason it is very important to write functional requirement document will be care. I will write another post. How we have to write functional requirement document and what things we need to care. Any how main point is your functional requirement document must be very good and that is the only thing that help us to close things. Specially when we unable to convince end user or key account holder.
Second way is Story telling. How good you are in Story telling. You can convince him easily.
Human mind did not thing straight. Any how point is simple and straight but it did not understand. It understand, what will happen, if we do that.
Remember, Every project failed not technically, it failed financially. In Project management. There are world triple constraint. Time, scope and cost. Any one increase in it will result in increase other two factors. And Same time Quality is increase. And Most interesting point in this triple constraint is Cost.
So we built a story and share him and he understand our point and project goes to next stage which was in our case go live.
These are seven steps we used to built a story.
So what is yours, What you made it help you more client.
Hope for the best.
2022 was one the best year of my life.
4 lesson I learned in 2022. Extracted from 4 Agreement book
-Understand the power of words. Change your voice in side your. Change the words
-Nothing is personal. Never ever take anything personal.
-Dont assume. Face the reality. Ask untill clear.
-What ever is the situation. Do your best.
Struggling to upgrade Devboxes. Certainly you find similar issue. I found similar. Time out error occurs on upgrade step of AOSService setup. It is most important step. Where new code injected into different models in Dynamics. We can not skip this step.
I faced this issue 10.0.30 service pack update which contains changes in Human Resource module. Any how I have to follow this step before rerun the step.
I update the xxxRunbox.xml file. You will find this runbook with same name which you created in initial setups.
Search step, there only update TimoutValue. Dont try to search and update 75 to 1800. It corrupts the file.
And then again import this runbook file
AXUpdateInstaller.exe import -runbookfile=”CRDEV4-runbook.xml”
After that go back to same point and run it again.
Problem solve.
What ever you do, there is always way to learn something. Buddah once said ““When the student is ready, the teacher will appear”. So Google his here for my teacher.
So today I decided to learn Business Central. And here is my first blog post.
While making my notes, these punjabi folk song comes in my mind, Also note it down.
jangal bele phiran dhoondendi ( I am searching my beloved rivers and forest)
ranjhan mere sange ( My beloved is with me in my mind)
nee menda dil ranjhan rawal mange ( My heart seeking you)
ranjhan rawal mange ( beloved name folk name)
majhian aaiyan meda dhol na aaya ( My fellows come back but my beloved not)
heer kookay vich jhange ( Heer calling her beloved name in forest madly)
lets go back to point.
On demo instance of Business Central allows only two demo companies. I created many.
And after fourth Company. Business Central stop working.
Its quite different form F&O. I found following error message
‘Your program License doesn’t permit support maximum N non-demonstration companies’
So my first search how to remove companies with powerShell so here are my notes for my future self.
first step to import commendlet module that comes to Business Central. Location is some where in c:\program files folder \ Business central\ Service
After finding that path Following command works
Import-Module ‘C:\Program Files\Microsoft Dynamics 365 Business Central\180\Service\NavAdminTool.ps1’
So it imported what next
Now I need list of Companies in local instance. For getting companies “Get-NAVCompany” command.
PS C:\WINDOWS\system32> Get-NAVCompany
cmdlet Get-NAVCompany at command pipeline position 1 Supply values for the following parameters: ServerInstance: bc180
so I get following list. And interestingly there are a lot of … Name there. And I created them.
Now I have to delete the Companies step by Step. On local installation as demo. There is no need of Tenant So following statement works for me.
Remove-NAVCompany -ServerInstance BC180 -CompanyName ‘Test Bab Jii’
Remove-NAVCompany -ServerInstance BC180 -CompanyName ‘Test my company’
Remove-NAVCompany -ServerInstance BC180 -CompanyName ‘CRONUS Pakistan’
After deleting These companies. BC instance started to work fine.
Recently I got interesting issue. I developed the report based on RDP Class. I have to populate temp table. And based on this temp table I have to aggregate some calculation like sum, Average on Group by.
But when I populate another table based on this aggregation. Report starts to go long awaiting state. I dont know the reason. Later I found that I did not give active connection to temp table variables.
I added following line of code in reports and report processing reduce to less then 2 minutes
this.takeOwnershipOfTempTable(_BEGroupWiseSalarySheetTmp);
this.takeOwnershipOfTempTable(_BEBranchWiseSalarySheetTmp);
Code suddenly breaks. When I debug I found intvNo method which used to calculate days interval between two dates is not working.
intvNo(empLeave1.EndDate,periodStartDate,IntvScale::Day);
I have replace it with following way.
date2Num(periodEndDate) -date2Num(periodStartDate);
