Customise Chart Part Crashes RTC

ryanatwork

Hi,

Trying to customise a Chart part for an upgraded database. Every time I do this in the Role Centre the RTC crashes.

My login is a super login.

Here is the stack trace :-

Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavFilterException
SuppressMessage: False
FatalityScope: None
Message: The filter 'Comany (Pty) Ltd. TEST|''' is invalid. You entered an invalid expression in the filter on the Company field in the Chart table.
StackTrace:
at Microsoft.Dynamics.Nav.Client.ExceptionHandler.<>c__DisplayClass2.<DoRethrowWithCatchException>b__0()
at Microsoft.Dynamics.Nav.Client.ExceptionHandler.ExecuteAndCatchExceptions(Func`1 execute)
at Microsoft.Dynamics.Nav.Client.ExceptionHandler.DoExecute(Func`1 execute)
at Microsoft.Dynamics.Nav.Client.ExceptionHandler.DoRethrowWithCatchException(Exception exception)
Source: Microsoft.Dynamics.Nav.Client

---

Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavFilterException
SuppressMessage: False
FatalityScope: None
Message: The filter 'Comany (Pty) Ltd. TEST|''' is invalid. You entered an invalid expression in the filter on the Company field in the Chart table.
StackTrace:
at Microsoft.Dynamics.Nav.Client.ConnectionStateManager.CallServer[T](CallServerMethod`1 callServerMethod)
at Microsoft.Dynamics.Nav.Client.ServerInvocationHandler.CallServer[T](CallServerMethod`1 callServerMethod)
at Microsoft.Dynamics.Nav.Client.ServiceConnectionBase.CallServer[T](CallServerMethod`1 callServerMethod)
at Microsoft.Dynamics.Nav.Client.ServiceConnection.GetPage(PageRequestDefinition pageRequestDefinition, NavRecordState& state)
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.ChartPersonalizationPanel.GetAvailableChartsForCurrentCompany()
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.ChartPersonalizationPanel.GetAvailableCharts(String selectedChart)
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.ChartPersonalizationPanel.InitializeControls()
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.PersonalizationPanel.OnParentChanged(EventArgs e)
at System.Windows.Forms.Control.AssignParent(Control value)
at System.Windows.Forms.Control.ControlCollection.Add(Control value)
at System.Windows.Forms.Form.ControlCollection.Add(Control value)
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.PersonalizationForm.set_PersonalizationPanel(PersonalizationPanel value)
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.PersonalizationForm..ctor(UISession uiSession, PersonalizationPanel panel)
at Microsoft.Dynamics.Nav.Client.NavUI.Forms.PersHomepage.CustomizeClick(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Source: Microsoft.Dynamics.Nav.Client.ServiceConnection

---

Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavFilterException
SuppressMessage: False
FatalityScope: None
Message: The filter 'Comany (Pty) Ltd. TEST|''' is invalid. You entered an invalid expression in the filter on the Company field in the Chart table.
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.NavRecord.SetFilter(NCLMetaField metaField, String expression, NavValue[] values)
at Microsoft.Dynamics.Nav.Runtime.NavRecord.SetTableViewFilters(NavFilterGroup[] filterGroups, Predicate`1 condition)
at Microsoft.Dynamics.Nav.Runtime.NavRecord.SetAllowedTableViewFilters(NavFilterGroup[] filterGroups)
at Microsoft.Dynamics.Nav.Runtime.NavRecord.SetTableView(NavTableView view)
at Microsoft.Dynamics.Nav.Service.NSDataSetState.ApplyToRecordWithoutPositioning(NavRecordState state, NsDataAccess recDataAccess)
at Microsoft.Dynamics.Nav.Service.NSDataSetState.ApplyToRecord(NavRecordState state, NsDataAccess recDataAccess)
at Microsoft.Dynamics.Nav.Service.NSPage.GetPageData(NavConnection connection)
at Microsoft.Dynamics.Nav.Service.NSPage.GetPage(NavConnection connection)
at Microsoft.Dynamics.Nav.Service.NSService.<>c__DisplayClass37.<GetPage>b__36(Connection connection)
at Microsoft.Dynamics.Nav.Service.NSService.ExecuteOperation[T](String operationName, ServiceOperation`1 operation, Connection connection, Boolean revertLanguageChanges, WindowsIdentity impersonationIdentity)
Source: Microsoft.Dynamics.Nav.Ncl

---

Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavCSideException
ErrorCode: 18023497
ErrorNumber: 1097
ModuleNumber: 19
SuppressMessage: False
FatalityScope: None
Message: The filter 'Comany (Pty) Ltd. TEST|''' is invalid. You entered an invalid expression in the filter on the Company field in the Chart table.
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.NavRuntimeAdapter.ErrorHandler(Int32 errorCode, Int32 errorNumber, Int32 moduleNumber, String errorText)
at Microsoft.Dynamics.Nav.Runtime.NativeMethods.AdapterSetFieldFilter(IntPtr connectionHandle, IntPtr tableHandle, Int32 fieldNo, Byte[] expression)
at Microsoft.Dynamics.Nav.Runtime.NavRuntimeAdapter.SetFieldFilter(IntPtr connectionHandle, IntPtr tableHandle, NCLMetaField metaField, String expression, NavValue[] values)
at Microsoft.Dynamics.Nav.Runtime.NavRecord.SetFilter(NCLMetaField metaField, String expression, NavValue[] values)
Source: Microsoft.Dynamics.Nav.Ncl

ryanatwork

Just tried it on a Cronus database in the same environment.

The crash seems to be caused by the brackets () in the company name.


Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavFilterException
SuppressMessage: False
FatalityScope: None
Message: The filter 'CRONUS Australia (TEST)|''' is invalid. You entered an invalid expression in the filter on the Company field in the Chart table.

This must be a bug ! I cannot find find any hotfixes tho ?

Strange :-k

preitzel

True .. this is a known bug and it will be fixed in the next release.

The only workaround you can do for now is to avoid the using of brackets.