Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to set the Downtime Cause Location to empty or null #3

Open
JoePlant opened this issue Oct 9, 2013 · 4 comments
Open

Unable to set the Downtime Cause Location to empty or null #3

JoePlant opened this issue Oct 9, 2013 · 4 comments
Assignees

Comments

@JoePlant
Copy link
Member

JoePlant commented Oct 9, 2013

When writing to the Ampla Data Webservice, if the Cause Location is null or string.Empty then web-service will throw the following fault.

    <s:Fault>
      <faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode>
      <faultstring xml:lang="en-AU">Value cannot be null.
Parameter name: name</faultstring>
      <detail>
        <ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
          <HelpLink i:nil="true" />
          <InnerException i:nil="true" />
          <Message>Value cannot be null.
Parameter name: name</Message>
          <StackTrace>   at Citect.Common.ArgumentCheck.IsNotNullOrEmpty(String argumentValue, String parameterName) in c:\Projects\Platform\v5.2\Code\Common\ArgumentCheck.cs:line 113
   at Citect.Ampla.Framework.ChildItemsCollection.get_Item(String name) in c:\Projects\Platform\v5.2\Code\Framework\ChildItemsCollection.cs:line 124
   at Citect.Ampla.Framework.AllItemsCollection.get_Item(String name) in c:\Projects\Platform\v5.2\Code\Framework\AllItemsCollection.cs:line 57
   at Citect.Ampla.Public.WebService.Data.V200806.DataWebService.buildEditedData(Int32 recordIndex, SubmitDataRecord record, Int32 setIdInt, ErrorHelper errors, FieldDescriptorCollection fieldDescriptors, Guid session) in c:\Projects\Applications\v5.2\Code\WebServices\Public\WebService\Data\V200806\DataWebServiceImplementation.cs:line 3019
   at Citect.Ampla.Public.WebService.Data.V200806.DataWebService.buildSubmitDataEditableCollection(ErrorHelper errorHelper, SubmitDataRecord[] sets, Guid session, String userName) in c:\Projects\Applications\v5.2\Code\WebServices\Public\WebService\Data\V200806\DataWebServiceImplementation.cs:line 2900
   at Citect.Ampla.Public.WebService.Data.V200806.DataWebService.SubmitData(SubmitDataRequestMessage requestMessage) in c:\Projects\Applications\v5.2\Code\WebServices\Public\WebService\Data\V200806\DataWebServiceImplementation.cs:line 945
   at SyncInvokeSubmitData(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc&amp; rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace>
          <Type>System.ArgumentNullException</Type>
        </ExceptionDetail>
      </detail>
    </s:Fault>


@JoePlant
Copy link
Member Author

JoePlant commented Oct 9, 2013

The consequence of this exception is that the Downtime Cause Location field is not able to be reset. It can only be set to another Cause Location.

If using Production Analyst, then the Cause Location can be set to "(blank)" or "Reset" using the context menu.

Ampla Version: 5.2.6135

@ghost ghost assigned alexmg Oct 9, 2013
@JoePlant
Copy link
Member Author

JoePlant commented Oct 9, 2013

@alexmg, I am not sure if this issue has been fixed in later versions of the SubmitData. This will cause an issue for both Add and Update operations.

@alexmg
Copy link
Member

alexmg commented Oct 9, 2013

@JoePlant I'll email this to myself at the office and take a look.

@JoePlant
Copy link
Member Author

JoePlant commented Oct 9, 2013

Thanks @alexmg, I have added a feature into the codebase where it will not submit a Cause Location that is empty or null.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants