Hi @kvbe ,At the time, we found that it was not working for users who had SSO enabled. Since my colleague and I were not using that, it was working correctly for us.
Hi @gesh , As per my knowlegde setting up document footers and document phrases etc. is a manual action you have to perform in each environment. There is no export/ import functionality in the client and these kind of things cannot be included in application configuration packages. The alignment in the reports itself is ofcourse stored in the report designer layouts and those can be exported and imported via the client. Best regards,Michael
Hi @GaSoGB,If you would like to have IFS handle the ID's I think the best way to go is using the standard functions IFS provides for this. For example, if you are going to do the migration of customer address then in the background it will use the CUSTOMER_INFO_ADDRESS_API method to create the new addresses. In that package you have the function Get_Next_Address_Id which needs the company and customer ID as input. The output of this function is the first available number to come as new address ID. I would assume that if you put CUSTOMER_INFO_ADDRESS_API.Get_Next_Address_Id(customer_id_, company_) in the default value column of your mapping this should work. Although this is from my experience with the 'old’ FNDMIG migration jobs. I haven't tested it yet with the data migration manager. I know the supplier address has the same function in the SUPPLIER_INFO_ADDRESS_API. Hopefully this suggestion will help you. Best regards,Michael
Hi @GaSoGB ,In the old migration tool we indeed defined the headers like CUSTOMER_ID, NAME etc. as these were the column names for the IC table. In the new data migration manager these headers are indeed less important. In the back IFS stores the legacy data in one big table. This table holds columns like C1, C2, C3 etc. This is fixed. That means that if you have CUSTOMER_ID and NAME columns, these end up in the columns C1 and C2 of this legacy data table. So when you are going to do the mapping of your legacy data you see two columns. On with the more functional column name and one column with the technical column name, which is C1, C2 etc. Eventually IFS uses only the C1, C2 column names. That is why the column names you provide in the CSV doesn't matter anymore. Please note that when you add a column in your legacy data, do it at the end as otherwise you have to redo the complete mapping. We can no longer add columns in between like we could do in the old migration tool. Hopefully t
Hi @GaSoGB, For as far as I know there isn't a specific place where these templates can be found. But I can share the 22R1 version which IFS shared with us.Hope it will help you. Best regards,Michael
Hi @Nikita38 ,Perhaps if you set the auto generated value for the supplier ID to FALSE and then try to change the values for the default language and country? Then afterwards you can set the autogenerated column back to TRUE.That is the only difference I see in regards to our setup. It might cause the conflict you are having. Kind regards,Michael
Hi @LindaK ,To change the appearance of IFS, you can use the appearance designer. In here appearance properties such as color, images, text and font can be configured.https://docs.ifs.com/techdocs/21r2/060_tailoring/220_configuration/925_user_interface/ Hopefully this helps.Michael
Hi @TheoB,Yesterday I was trying the same thing and found out that it seems not to be working in the IFS Cloud. A colleague of me pointed out the following community post about this: It seems like a bug that it is missing as the documentation states it's one of the migration rules that should work. Howerver it was reported as a bug but not solved so far I know as I tested it yesterday in 22R1. Kind regards,Michael
Hi @TheoB, When creating the Excel migration job you have a rule named FETCHCONDITION. This is where you can join other tables but also add where clause conditions to fetch less data. This is what the documentation says about this:FETCHCONDITION Keep this to Active if the job should have Query functionality from the Excel add-in (Query enabled jobs). If the job contains multiple logical units, this field should contain the join clause between the logical units. e.g. SUPPLIER_INFO.SUPPLIER_ID = SUPPLIER_INFO_ADDRESS.SUPPLIER_ID AND SUPPLIER_INFO.SUPPLIER_ID = SUPPLIER_ADDRESS.VENDOR_NO..If you want to add additional filtering you can add it here as well. (e.g. SUPPLIER_INFO.COUNTRY_DB = ‘LK’)https://docs.ifs.com/techdocs/21r2/045_administration_aurena/260_data_management/050_data_migration/030_migration_types/030_excel_migration/Hope this helps.Kind regards,Michael
Hi @Miguel, By using pragma autonomous_transaction in the declare section of your code you can query the table that also contains the trigger. So you will be able to fetch the category1_name eventhough the table is mutating. You can find more about this here: on https://docs.oracle.com/cd/B19306_01/appdev.102/b14261/autonotransaction_pragma.htmI hope this helps. Kind regards,Michael
Hi @ChanakaAmarasekara ,The latest version you are referring to is from may 9th. I already installed that and it's still not working. In 21.2.0 SU7 it was working for a while. So it's strange that now in 22R1 it's not working anymore. Kind regards,Michael
Hi @Dinari Nanayakkara, I'm wondering if that would work, as I've also tested it against a cloud demo environment which has the newer version 22.1.0 and that is also not working. Still when I want to preview the report it just says it's rendering, but then opens nothing… Kind regards,Michael
Hi @Dinari Nanayakkara, The version this issue is occurring in is version 21.2.0 Kind regards,Michael
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.
