I passing the following to LoadRunner:
<makeAtmPayment xmlns=\"http://[URL]" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">"
"<billerId>BILL01</billerId>"
"<userId>950002</userId>"
"<productCode>P1</productCode>"
"<productParameter><value>923</value></productParameter>"
"<paymentChannel>PAY01</paymentChannel>"
"<paymentAmount>2</paymentAmount>"
"<convenienceFee>1.50</convenienceFee>"
"<effectiveDate>2011-04-14</effectiveDate>"
"<accountId xsi:nil=\"true\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"/>"
"<atmCardNumber>564373636363636</atmCardNumber>"
"<editedConfirmationId xsi:nil=\"true\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"/>"
"</makeAtmPayment>"
and it's throwing me the following error:
InvokeMethod failure: Unable to deserialize non XmlElement node #text in path '/makeAtmPayment/productParameter/name/#text'.
Can anyone give me any pointers on what I am doing wrong ?
Thanks!!
Try to change
<productParameter><value>923</value></productParameter>
To
<productParameter><name>923</name></productParameter>
I don't understand the double quotes. There is one missing at the very beginning and there is one without a slash after xmlns=\"http://[URL]". Could it be the problem?
Is this an XML of your own creation or one picked up off of a loadrunner recording? If it is the latter consider recording twice to see what differences get picked up that you need to accommodate during your development. If it is the former, then consider validating your XML through the application's business rules before submitting it via LoadRunner, just to ensure that the XML is sound independent of your testing tool
Related
Transformation Parse Warning [<<P M Parse Warning>> <<Invalid constant sun-expression>> <<Expression Error>> [TO_DATE]:invalid string for converting to Date
… t:TO_DATE(s:s:”,s:s:’YYYYMMDD’)
……….
AND SATIS_TARIHI = >>>> TO_DATE($$RUN_DATE,’YYYYMMDD’)<<<<];
How can I solve this?
This is the first time I encounter this error. Normally, this is a daily routine for our job. The parameter is successfully added to the mapping and all the other things seem okay. I’d appreciate your help.
I tried to start the workflow and got this error.
You need to define a $$RUN_DATE in mapping. Currently its not defined in mapping or its null in parameter file.
You need to set a default value in mapping like 20221221 for today.
Or else you can set it up in a parameter file like this
[folder.workflow_name]
[folder.session_name]
$$RUN_DATE=20221221
Considering this is your daily routine and up till now it has been working fine, I assume this is not a new development and no recent changes have been made. Apparantly PowerCenter got an invalid value for the parameter.
Check you parameter file and how it gets generated.
Was the process of generating paramfile executed without issues?
Was there enough storage space?
Can you verify the paramfile contents?
Can you regenerate it?
Can you modify it and provide some value manually?
Feel free to get back with some updates for more help if your problem won't get resolved by checking the items on the list above.
To all
When trying to open an asset (DRL or Legency Test), I receive the message "Unable to complete your request. The following exception occurred: name is empty."
I can't find any hint what this means. My rules import from different projects which all can be accessed.
Does anybody have an idea what this could mean? Thank you very much already in advance.
big hug
Michael
I found out by myself. The external data objects configuration had an empty entry. So be careful when adding an external data object - you are able to add an empty row and Business Central let's you save this ... with the empty row causing the error described.
happy coding
Michael Lutz
I'm creating a project to mail merge a given .odt file and provide a .odt output. When i'm performing the mail merge operation it provides me this error
TinyButStrong Error in block's definition [CiviCRM.display_name...]: at least one tag corresponding to w:tr is not found. Check opening tags, closing tags and embedding levels.
Myfilecontent.odt
[CRM. display_name;block=w:tr]
Date: 2/3/2020
Dear [CRM.postal_greeting;block=w:tr],
Thank you for joining the event...
I have no idea how to resolve this. could someone help me to solve it?
Thanks in advance!
Update
After i replaced w:tr with tbs:row, still I'm receiving a similar error
TinyButStrong Error in block's definition [CRM.display_name...]: at
least one tag corresponding to tbs:row is not found. Check opening
tags, closing tags and embedding levels.
w:tr is an XML entity for Ms Word , not ODT.
You should use the alias block=tbs:row so that its is format independent.
I'm trying to embed Jasper Reports into APEX App. I'm able to gather reports from samples (samples on JasperCommunity website), however, when I'm trying to get created by me and colleagues reports - every time I have the same error:
JSON schema validation failed: resource: String does not match pattern: ^/[^/~!#\$%^|\s#&*()\-+={}\[\]:;"'<>,?/\|\\]+(/[^/~!#\$%^|\s#&()-+={}[]:;"'<>,?/\|\]+)$.
In other words I can't get any of our reports apart from the samples (e.g. /public/Samples/Reports/03._Store_Segment_Performance_Report"). I think the case is that the path to the Report is wrong, but I've tried all possible and impossible options and none of them works. Anyone any ideas please ?! Thanks
P.S. APEX 4.2.6, JasperServer 6.0. And finally, I can get samples Reports ONLY under the JasperAdmin user, simple User always got an error - 'Access Denied'. Why ?!?!?!
Sorted.
If anyone interested - when specify the actual path, in Jasper: right click on Report(or Dashboard, AdHocView etc.) and copy the path from it. As it differs from when you point mouse on it (e.g. adding the underscores etc.), and paste this actual path into your javascript code into HTML section in your web app. Thanks
In Selenium I recorded a test suite and while executing I received the script error:
Element id=ui-id-12 not found
You are getting this error because you have recorded wrong script. The element ID 12 is changing every time. So you can use another way to detect the Web-Element.You will have to use more preferred way of locating the Web-element. Instead of using id please try to use static attribute of the Web-Element. I believe it will fix your problem.