User Profile

CarolMonzillo

New Contributor

Joined 8 years ago

5 Posts9 LikesLikes received

View All Badges

User Widgets

Contributions

Remove days from excel spreadsheets.
When exporting a report to excel, the total time of a report is in the format 18d 20:30:50. Convert this to a number that Excel understands so arithmetic is simple.
4 years ago Place Collaborator Questions
567Views
1like
1Comment
reviews taking a very long time to load
has anyone else seen a problem with reviews taking a very long time to load? They can sometimes takes hours. Then if you try to do it again later in the day, it comes up quickly. Very strange.
Solved
4 years ago Place Collaborator Questions
1KViews
1like
1Comment
XML document structures must start and end within the same entity.
I am getting the following error intermittently for some reviews from ccollab. Incidentally these reviews can take forever to come up. Have anyone else seen this? ccollab admin review-xml 1 --xpath //reviews/review [Fatal Error] :3:22: XML document structures must start and end within the same entity. ERROR: Executing command `ccollab admin review-xml`: org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 22; XML document structures must start and end within the same entity. com.smartbear.collaborator.client.exceptions.CollabClientException: org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 22; XML document structures must start and end within the same entity. at com.smartbear.ccollab.client.commands.CommandAdminReviewXML.executeJson(CommandAdminReviewXML.java:288) at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:360) at com.smartbear.ccollab.CLI.doMain(CLI.java:912) at com.smartbear.ccollab.Main.doMain(Main.java:219) at com.smartbear.ccollab.Main.main(Main.java:167) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:85) at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) Caused by: org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 22; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at com.smartbear.ccollab.client.commands.CommandAdminReviewXML.executeJson(CommandAdminReviewXML.java:28
4 years ago Place Collaborator Questions
2.7KViews
0likes
1Comment
Make Collaborator work with LabView
Currently doing Peer Reviews with LabView does not work. The users would like to be able to put comments on the LabView diagrams. Saving each file to pdf to be able to comment on each is not a great solution. There can be many files and files are coordinated with each other.
8 years ago Place Collaborator Feature Requests
4KViews
7likes
1Comment
Has anyone tried to use Collaborator with LabView?
We need to use Collaborator to review LabView code. Since you cannot bring up the LabView tool with Collaborator we are thinking of having the author create links to the labview code in a custom field. And then put all their comments into the overall defects area since there will be no files associated with the review. Does anyone else have any suggestions on how to do Code Reviews for files that can not be displayed inside of the Collaborator tool?
8 years ago Place Collaborator Questions
1.8KViews
0likes
2Comments