Skip to main content

Hi,

I have SharePoint list with Rich text column "Description". I am calling Web service action in Nintex workflow with Description Column value.

For empty paragraph tags "<p></p>"  call web service action is adding question tag like "<p>?</p>".

I printed the values before calling web service action("<p></p>") and values received at asmx service function("<p>?</p>") both are different.

I have selected Encode inserted tokens It seems encoding inside call service action causes this issue.

Please validate this issue and suggest me.

Regards,

Gunesh v

do you have any control over that formatting?

to try change paragraph tag to <p /> or <p>nbsp</p> whether it will work correctly that way.


Yes we can format the html. However I want to understand why it is happening during web service action.


is it any specific web service?

or do you experience it generally?


I am talking about "Call web service" activity of nintex workflow.

188351_pastedImage_0.png

To reproduce this issue

1. Create a test webservice with a function that prints parameter value.

2. create a sharepoint list with rich text column.

3. Create a workflow that starts on item creation and calls webservice. pass rich text field value to it.

4. add a new item with "<p></p>" in rich text field. and check webservice printed value. It will be "<p>?</p>"


so, are you querying you own web service?

are you sure it's configured properly?

I've setup my own test scenario and do not see any problem.

action configuration

when I open run now I get encoded HTML elements. no question mark so far.

and this is what I receive when I execute service call.

within requestReceived tag web service simply returns me back what it received on input.

so no question marks in my case

and this is what I get logged by web service


Hi Marian Hatala,

Thanks for your support and sorry for delayed response.

Actually i am pushing data to SQL table using "Call web service" action. Issue is with SQL field data type. I changed from "text" to "nvarchar" issue got resolved.


Reply