Hi @Siva Ganesh M , To my knowledge this is not possible - you would need two Excel DM jobs. One for New, one for Update - I understand this is not what you’re after. If you have a techie there that is hot on VBA then pass this requirement to them - maybe they can embed a macro into a saved Excel DM workbook to retrieve the WO No. Cheers, Pete Thanks Pete for your valuable tips. I have managed by configuring another Excel migration - Search job to pull the data in to Excel. This is achieved by mapping a field with a unique value for each Excel Migration job run and using this field as an input parameter in the Excel migration - Search job to pull the data. But it will be good and needed functionality, if write back to excel is made possible in future releases. Thanks & Regards, Siva
Hi Pete, Thanks for looking in to this. I am using IFS 10 UPD4. The issue is with the Base Profile only. I have a screen in which the layout was changed to suit customer requirement and maintained in the Base Profile. The profile values are stored against the screen name ‘frmXXXXX’. Lately we customized this screen to add some more real fields & RMB options. The frm name changed to ‘frmXXXXX_Cust’. After deployment, in front end when we open this screen, it automatically opens the customized form ‘frmXXXXX_Cust’. if Base Profiles is attached to the user, it opens the Standard screen frmXXXXX, since the base profiles is not automatically updated with the customized form on deployment. I am not sure whether it is a missing functionality or we are missing something during customization. As of now i have found an work around. Exported the base profile and replaced all the entries from frmXXXXX to frmXXXXX_Cust in the XML. Imported back the XML which worked. May be i have to do s
Antony,Thank you very much. Just to clarify the core product what do you mean here is the eBuyer solution which is offered as extension (VAP).Any Roadmap / Timeline if you know for including this in Core solution. Thanks & Regards, Siva
Thanks for quick response Sampath & Johan.All the Parts needed to be sync to the mobile for the below scenario: Material requirement for a task is done mostly in Mobile based on actual being used during WO execution in Mobile Returns are planned in the Mobile.In both the above scenario, No list of part available if the parts are not synced and in current customer data setup there is no specific list of part / spare part data is maintained at object level or in the Work Task template. Still working with Business to see how can this be filtered and limit the parts being synced to individual mobile users.Thanks once again for the detail clarification on my query. Regards, Siva Ganesh M
Thanks for the quick response Maura Wasantha. Regards, Siva Ganesh M
Thanks Sampath.. Can this is taken as a patch for UPD7.Thanks & Regards, Siva Ganesh M
Thanks Sampath.. Somehow I am not able to open the attached link. Instead I got another solution ID: 288013 which is for the same issue. I am not sure are you referring to the same one. If not please let me know the Solution ID. Thanks & Regards, Siva Ganesh M
Thanks for confirming Sampath.I will check with our technical to get the patch and deploy in our IFS10 UPD7 environment. Hope this will solve the issue. Thanks once again for your prompt response and help. Regards, Siva Ganesh M
We have applied the patch from solution ID: 288013 in IFS 10 UPD7 , But the issue is not solved. Any view and comments will help here. Thanks & Regards,Siva
HI, This is not yet resolved. The last update isWith some assistance from IFS RnD, it is found out the issue is with UPD 7 environment.For these file selectors there is an "Enabled" attribute. You can specify the enabled attribute specifically to be "true" or "false", but you can also not use it in your code. However, in UPD 7 code generation if you do not specify it, the code will generate this as an empty value.From UPD 8 onwards the code generation defaults this Enabled attribute to True. So basically, right now in UPD 7 code generation, the file selectors are not enabled. Code generations changes cannot be applied to a single patch, we can only take the next UPD where this is fixed. Thanks & Regards, Siva
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.