tag:help-archives.hannonhill.com,2010-02-09:/discussions/web-services/622-web-services-fail-to-conform-type-issueCascade CMS: Discussion 2014-03-25T20:54:23Ztag:help-archives.hannonhill.com,2010-02-09:Comment/243182372013-01-29T01:13:34Z2013-01-29T01:13:34ZWeb Services Fail to Conform: type issue<div><p>after further testing:</p>
<p>the authentication/asset structure is correct - I can save an
xhtmlDataDefinitionBlock with an edit request with a change to the
name or etc...</p>
<p>the issue appears to be with changes to data definition values
in the block... specifically adding or altering a repeating block
or file chooser.</p>
<p>when changing a repeating file chooser via WS Object (PHP), WS
does not allow additional repeating file choosers to be added, or
for existing repeating file choosers to be edited. After editing an
existing asset, that same asset fails to save via WS.</p>
<p>I can confirm that the file chooser can be repeated and saved
within Cascade, with the same values I am attempting to save via
WS, and it save fine.</p>
<p>I can also confirm that the only part of the WS object that is
being edited is the repeating file chooser, and that the data being
saved there is in no way causing Cascade WS to choke.</p>
<p>Let me also add that WS does seem to be able to remove repeating
file chooser content, however, these changes don't show up in
Cascade's editing feature, which still reflects the old attachment.
Instead, they can be seen in WS, and in the "view" mode of Cascade
for the block.</p>
<p>Whatever is going on with this is causing me a headache and
interrupting my ability to get anything done via WS.</p>
<p>Cascade 7.0.5</p></div>christiancotag:help-archives.hannonhill.com,2010-02-09:Comment/243182372013-01-30T14:11:22Z2013-01-30T14:11:22ZWeb Services Fail to Conform: type issue<div><p>Hi Christian,</p>
<p>I wanted to follow up to see if you had a chance to read my
<a href=
"http://help.hannonhill.com/discussions/requests/3899-web-services-issue#comment_24361645">
recent comment on your Support Request discussion</a>.</p>
<p>To avoid confusion, I am going to go ahead and close this
discussion.</p></div>Ryan Griffith