June 30, 2018

How to create default Data packages Dynamics 365 FO

Hi Folks,

Now we all know how powerful and useful is LCS for Dynamics 365 projects. There are a lot of tools to manage your project efficiently and their powerful tool helps you to manage your project well. For any project Data management (import and export) is very essentials milestone for any environment and this can surely be a time consuming and lengthy if we are not using the right tools.
Well, LifeCycle service (LCS) provides a powerful tool to manage the data import and export for a project. Configuration and data manager tool (to import data package, will cover in next post) allows selecting multiple data packages and import in any environment for a project. In this article, I will show how to create default data package in LCS asset library. This tool will help you create the default template in a sequential manner.
(However, I planed a long back to write this article but…. Winking smile I hope its never too late. )
Let's start…..
1. Login into https://lcs.dynamics.com/ using your organization credentials.
2. Select the project and go to Asset library > Process data Package; if you didn't see this tool icon on project landing page then try below
image
You can see we have only 2 files here.

3. Now to create default packages click on Import button and select a library from the list,
image

4. The above step will create a new record in process data package, it will create the data packages under ‘Data package’ tab in Asset library.
image

5. Once this process done you can go back to configuration and data manage toll you can see all the packages available here. You can download them, you can import them into any other environment. Also, you can download and fill out the data and upload them back on LCS to deploy these package on another environment.
image

Thanks all for the subjected topic, the below few details to explore further,

You can also update the Data packages (add new records, remove associate business process etc, ). To explore this go back to Asset library and click on your record and follow below steps.
image


In the next screen (Add data packages) you will see the list of all packages with sequencing number.
image

Also if you click on each package in above list in right window you will the details for the selected package.
Click on next> Next and complete this wizard.  (for this post don’t select anything on 4th step ‘Associate business process to data package’)

Cheers
Harry

June 11, 2018

[Solved] display method 'salesPcsPrice' defined on 'InventTable', referenced in data source *****

Hi Folks,

During some RnD on On hand inventory form, I have to duplicate the InventOnHandListPage, and while compiling this new form I was getting below error (even without any changes)

1. display method 'salesPcsPrice' defined on 'InventTable', referenced in data source 'InventTable_DS' of form '<FormName>', returns type 'Price', which is not recognized. Are you missing a module reference?
2. display method 'inventUnitId' defined on 'InventTable', referenced in data source 'InventTable_DS' of form '<FormName>', returns type 'UnitOfMeasureSymbol', which is not recognized. Are you missing a module reference?
3. display method 'purchPcsPrice' defined on 'InventTable', referenced in data source 'InventTable_DS' of form '<FormName>', returns type 'Price', which is not recognized. Are you missing a module reference?




The best solution I found for this issue, is:
Go to the method which causes this error > Check the method return type> check the respective EDT >Chcek the package.

Now chcek you model parameters if the EDT model refering to system model as well. If this model is missing in reference, add it and update the model parameter.



After model parameter update, build your model and these errors must be fixed.

Enjoy.!!
Harry

June 08, 2018

Solution: Build error for new class in D365FO

Error: The model element was saved with unparsable source code and cannot be used. Please edit the element in Visual Studio to fix the errors: <ProjectName> (CUS) [<Modelname>] K:\AosService\PackagesLocalDirectory\bin\XppSource\<ModelName>\<ObjectName>.xpp



Possible reason: Sometimes when we rename the object name in code and manually rename the object from Solution Explorer, respective metadata still pointing to old names. Ideally, it should be another way around, rename the object in solution explorer and then just open the object it will automatically rename in class code.

Suggested Solution:
This issue doesn't fix even after DB synch and Model build. The only solution I can find for this issue is by deleting the object and create a new one. Yes, delete the object and create a new one with same code and name. This should fix this error.
Let me know if you found some other fix for the same.

Cheers
-Harry

June 06, 2018

Every single eBook and video is available for just $10

Hi Folks,

Packtpub are on sale, Every single eBook and video is available for just $10





-Harry Follow us on Facebook to keep in rhythm with us. @Facebook