Latest info I got was that they keep a 14 days backup but I do not think you can get a backup yourselves. Only for emergency cases
@MMcK indeed, removing the _TAB makes it, that it works! Thanks for that!
@NovPeterR we got the following response regarding this issueSo key is that you should leave the sequence field blank in the migration job!Hope it helps!ROOT CAUSE: - Next Number of db sequence INVENTORY_LOCATION_SEQUENCE is '111' (Refer image NextNumber.png) - Field LOCATION_SEQUENCE in WAREHOUSE_BAY_BIN_TAB is getting the values from sequence next value. - But the maximum existing value of LOCATION_SEQUENCE in WAREHOUSE_BAY_BIN_TAB is '15467' with migrated data. (Refer image UATMaxSequence.png) - Currently, when inserting a new record to WAREHOUSE_BAY_BIN_TAB, the next value of sequence 'INVENTORY_LOCATION_SEQUENCE' is fetching '111' (On each insertion sequence value increased by 1) an already existing value for LOCATION_SEQUENCE in WAREHOUSE_BAY_BIN_TAB. Therefore, 'The Warehouse Bay Bin already exists.' error is thrown. As explained before, this has been caused from migration data and sequence was not updated accordingly. SOLUTION : Need to update the next value of db sequence 'IN
Hi Aleksandra,I tried it and this worked. I assume its the fact that it should be UPPERCASE PROD_STRUCT_ALTERNATE_API.BUILD__ R,Koen
Thats a very good suggestion! That should actually be a feature request. That the Excel migration tool should be named with an indication for the platform you are on.
@kathlk if you arrive in such a situation, can we fix this by reverting some deliveries and then apply them again? Does IFS cloud support a mechanism to revert a delivery?
I would give the excel migration a try as well. On TESTCreate an excel migration job for your SRV_REQUEST_CFV view Grant the right projection to a permission set for your user for the excel migration job Download the manifest file create an online excell file, insert , addin and upload the manifest for TEST Login, search for your view and loadOn PRODUse the exact same procedure Open a new excell file Load the manifest file Copy paste the data from one sheet to anotherSome issues with thisYou cannot export/import Excel migration jobs it seems Do not forget to set your permissions for your user. Be carefull to not upload the wrong data to the wrong platform. You will not see a full line by line error log, but if it comes from a TEST system it sort of should work.
To me it looks like you can add two excell addins to an Office environment. You can create an excell file for the TEST env and another one for the PROD env.(Note that you have to download the manifest for both environments then, TEST and PROD)Then you can just copy paste the data from one excell file to another.Note that you cannot export Excell migration jobs so you have to recreate the job in the PROD envand grant the needed access to the excell migration projection.
Hi! In order to better help you, could you add some screenshots of your two jobs you created?Maybe the column is not mapped?Maybe the modify setting is not set? so some screenshots of the 2 jobs would be great!
what is the end goal regarding your data?You could use Quick reports to list your values based on a query? (And then export all columns) you could create an excell migration job and load the data like that? Not the easiest to setup but once you get it, its quite nice to use for quick data loading. I would say, it depends a bit on your end goal of what you would like to do with the data?
Looking at other messages regarding these two tools I think this is the idea:The data migration tool is the more “old” way of migrating data and will be phased out The new way is using the Data migration manager and will become default in IFSSo based on this reply It looks like it is good to start to migrate to the Data migration manager (or old name Smart data manager) There is a course on IFS Academy and you can find some information about it in the Technical documentationhttps://docs.ifs.com/techdocs/22r1/030_administration/050_data_management/080_data_migration_manager/Hope this helps!
Just a small bump for this item. Is this some confirmed bug?
@Vimukthi Mahakumbura Can you reset the location sequence? Or indicate what the next number should be? or do you need to trace it in the migration job where a potential mistake has been made?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.