We have done a web access deployment on 10.1.600.X versions. We have noticed that on the web forms where there is any customization (like customer form) the search button and the file menu (including the top tool bar and the side menu) does not work. Also if you give the customer id and tab out , the form does not retrieve the records of the customer . In the standard forms where there is no customization we are not facing this issue . Any inputs to resolve this ?
May be, that you must use, “Generate Web Form” option in Menu Action from “Customization And Personalization Maintenance”
1 Like
Please suggest , System is throwing below error " Please set up a valid Web Application Folder and URL on the Company Maintenance form."
If you look at the help for the field, it tells you that should be pointing to the physical inetpub folder for your instance of EWA
Please suggest me on below points
-
How to attach customization in WEB Form.
-
We have “Generate Web Form” for Dashboard. But when we are trying to open through EWA. System throwing error (Refer to below screen)
When we are directly putting the URL in Web Browser, It is working fine (Refer to below screen)
http://epicor10/EPICNEW-EWA/ice.ui.app.b_fund_trans_tracker.epihostform.aspx
Dashboard is working fine now. I did following changes
-
Deploy UI Application (Refer to below screen)
-
Generate Web Form (Refer to below screen)
- Recycle IIS application.
For customized and UD forms we processed the below steps
- Verify Customization
- Run Customization
- Generate Web Form
While Generate Web Form, System is throwing below error
Application Error
Exception caught in: mscorlib
Error Detail
Message: Exception has been thrown by the target of an invocation.
Inner Exception Message: Object reference not set to an instance of an object.
Program: CommonLanguageRuntimeLibrary
Method: InvokeMethod
Client Stack Trace
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Ice.Ewa.MetadataExtractor.AssemblyLoader.TranslateCustomCode(String vdir, String assemblySubFolder, String uiappFormName, Boolean isDevMode)
Inner Exception
Object reference not set to an instance of an object.
at DDW.ExpressionStatement…ctor(ExpressionNode expression)
at DDW.Parser.ParseStatement()
at DDW.Parser.ParseBlock(BlockStatement node, Boolean isCase)
at DDW.Parser.ParseIf()
at DDW.Parser.ParseStatement()
at DDW.Parser.ParseBlock(BlockStatement node, Boolean isCase)
at DDW.Parser.ParseIf()
at DDW.Parser.ParseStatement()
at DDW.Parser.ParseBlock(BlockStatement node, Boolean isCase)
at DDW.Parser.ParseTry()
at DDW.Parser.ParseStatement()
at DDW.Parser.ParseBlock(BlockStatement node, Boolean isCase)
at DDW.Parser.ParseMethod(IType type, QualifiedIdentifierExpression name)
at DDW.Parser.ParseClassMember()
at DDW.Parser.ParseClass()
at DDW.Parser.ParseNamespaceOrTypes()
at DDW.Parser.Parse(TokenCollection tokens, List`1 strings)
at Ice.Ewa.TranslationTool.TranslationEngine.parseFile(StreamReader sr, String fileName, RulesManager rules)
at Ice.Ewa.TranslationTool.TranslationEngine.TranslateCustomCode(ILaunch Sender)
Please suggest me, how to Generate Web Form for UD customized forms & other customized forms.
Hi Hari_Dutt,
did you find out anything related to your last post ? I am facing the exact same problem when i generate web form for a customization.
Check your Metadata path in Company maintenance. It needs to be set the IIS Virtual directory (that is set for Sharing, Everyone=ReadWrite) using the UNC path eg. \server\sharename\EWADirectory
Thanks MikeGross, this is a point we already had to correct. Since then, we were able to use EWA, generate web forms and deploying configurators to EWA.
However, some customizations produce this error when generating web form.
I am now suspecting that this could be due to our referenced DLLs on customizations. Do you know if there is any limitation to reference DLLs and still generating web form for EWA ?
Pretty sure the webforms cannot use referenced DLLs, but I’m not the expert on EWA. Just thinking that I cannot see how IIS would be able to execute external references in C# code. I would think that the code would have to be part of the customization rather then external for E10 to compile the code into the webpage.
Yes. We have generated the web form for a customization.