Downgrade / import XPO from 2009 to 4.0 - dynamics-ax-2009

Is there any tool / automatism to import an XPO, exported from AX 2009 to AX 4.0?
The straight way does not work, since properties listed in XPO differ, e.g. I get the exception that import has been cancelled because of "...PROPERTY found, DATASOURCE expected..."
Only information I found is the one linked
Any tipps are appreciated!
#edit:
After testing and trying - import partitially works.
What I'm missing are:
indices on tables
fieldGroups on tables
deleteActions on tables
relations on tables

You can't out of the box "downgrade" projects. You can migrate code to the next version but you can't go backwards.
With that said, if you can import some kinds of objects is by accident, but it is not a supported feature. But you can export objects one by one (or type by type) and then try to import the ones that don't fail and replicate manually the ones that throw errors.
Another "solution" is try to modify the XPO manually based on the received errors during the previous step, but this is totally undocumented and will be doomed to try-and-error.

Related

Error in Design studio while importing t24 versions

I am trying to import Temenos T24 versions from DataBase to Design Studio. I can easily import all kinds of data using import option in DS, except T24 Versions which are not importing. And while importing I got error message like "Unable to import, Unordered add not supported". Any idea regarding the import versions in data.eson format?
You need to import T24 Versions using option "Import T24 Screens", and you need to import the versions, i.e. screens under "xxxxx-models" project. Best to create a separate folder, like "L3" under your "-models" project.
Same goes for Enquiries, Menus, Composite Screens and Tabbed Screens.

How Can I Be Certain a Microsoft Dynamics 365 Managed Solution Patch Roll Up Worked As Expected

I have a solution for dynamics 365 online that I control as unmanaged in git and deploy to production as managed. We have applied a number of managed patches into production and now want to roll up the changes. Reading [1] the process seems to be that we need to export the a new managed solution and roll up the patches in production to that new solution. How can I be certain that my new full solution hasn't lost anything from the old solution plus patches?
As an example, given I have:
Managed solution 1.0.0.0 in production
Patches, 1.0.1.0, 1.0.2.0, and 1.0.3.0 also deployed managed to production
…then how do I obtain a managed version 1.1.0.0 in production that looks identical to the 1.0.0.0 plus patches code?
[1] https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-patches-simplify-solution-updates
Unfortunately you may have approached this incorrectly by importing the patches into your target environment as managed solutions, and I'm not sure what your options are.
The correct approach assumes (in my practice) 3 environments:
DEV. This is where you have your unmanaged solution. You create and export your patch solution here
TEST. You import your patches here and verify everything works. Once everything is working you use the Clone Solution to roll your patches into a new major version. You export this new major version as a Managed Solution
PROD. You import your new Managed Solution here. Because it has a new major version, it overwrites / replaces your existing solution
In your TEST environment you should be able to select the "main" solution (i.e. version 1.0.0.0) and then click Clone Solution. This will allow you to specify a new major version number (e.g. 1.1.0.0). It will then automatically "roll-up" all the patch solutions - assuming that you created the patches using the patch process
From the article you linked
For a managed solution ... [y]ou
first clone the unmanaged solution (A), incorporating all of its
patches and then exporting it as a managed solution (B). In the target
organization that contains the managed version of the (A) solution and
its patches, you import managed solution (B) and then execute
DeleteAndPromoteRequest or the DeleteAndPromote Action to replace
managed solution (A) and its patches with the upgraded managed
solution (B) that has a higher version number.

Upgrading MVC 3 to MVC 6 What is the best way

I am planning to upgrade MVC3 EF5 project to MVC6. I understand it will require a lot of manual changes all over in config files, project files, entity framework, etc. Before I spend hours, wanted to see what is the best way?
Option 1: to make changes in IDs, configures, assemblies, etc. in the existing project (it doesn't even open in VS2015 right now, like any other MVC3 project, Thank You Microsoft). Looking at the instructions for converting MVC3 to MVC4/5, I guess I will need to have an ambulance on the standby here :-) It amazes me that MS did not provide any tool or even clear instructions to help developers.
Option 2: Create a brand new project in VS2015, then add new controllers with the same name as found in the old projects, then copy and paste controller implementations. Views and non-controller classes should work without much changes (only change I can think of is that new versions of dependencies in imports may be incompatible and will need to be dealt with manually, but this would be the same in Option 1). Not sure how to deal with entity framework. Perhaps if I recreate the entity model from database again, it should generate a compatible code. But then there are probably about 100 stored procedure function imports. I guess I will need to create function imports manually one by one (Question here, will the existing function imports remain intact if Option 1 is followed? Is there a way to copy function imports from the old project?).
Sorry, I know this is a rather convoluted question. Just trying to solicit inputs from others who may have done this in the past. I understand both Option 1 and 2 will require hours of work.

Add function import functionality seems to be broken in EF6

I am trying to import a function into my entity model. I am running VS 2012, using Entity Framework 6 with the according tools and yet no stored procedures or function names appear under the relevant drop down in the "Add Function Import" dialog.
Does anyone else have this issue? If so, does anyone have a solution?
Check your database user permissions, I think it needs ddladmin, at least that fixed it for me.

Resolving imports not found errors in Flex/Adobe Flash Builder

I am very new to Flex/Adobe FlashBuilder and I am running into an "import not found" error. Coming from a Java background, I understand this is more of a question of importing the equivalent of *.jar files in Flex/Flash. But how exactly I should go about resolving this, I am unaware.
Anybody want to help and get some points :) ?
If you're a beginner probably everything you import is included is Flex framework or is made by you. If you import your own classes remember to preserve package in their names (if the come from different package). Check classes names for spelling errors.
When using class in code you can use content assist (Ctrl+Space), then imports will be added automatically.
You can also check what quickfix lightbulb says (it's the same as in Eclipse as FBuilder is based on it).
You can make your question much better by including the code that causes the error.

Resources