Skip to main content
S
Sherri_McCue
Participant
February 14, 2017
Question

Validation Error Messages Not Logged In Console Window (FM12)

  • February 14, 2017
  • 1 reply
  • 2010 views

When I save a structured documents as XML (File -> Save As – XML), messages and errors appear in a Console Pod but are not reflected in the Console Window or in consfile.txt

Any help appreciated.

This topic has been closed for replies.

1 reply

S
shoose
Known Participant
March 11, 2017

I have this problem also -- I need to capture the validation errors somewhere, but they are not logged to consfile.txt.  Is there a setting somewhere that controls what is written to consfile?

I am using FrameScript also, and have not yet found a way to capture these validation errors from the console pod and copy them to a file somewhere.

This seems like a serious bug or issue in Frame, that errors just disappear and are not logged anywhere, unless there is a workaround.

I'm now on FM 2015.

Thanks much,

Shelley

W
Wiedenmaier
Inspiring
March 14, 2017

I'm never used the console.txt file for error handling in all the years.

XML messages that appear are validation issues mostly. So you can check the root element if structure is valid after document is opened or before it is saved.

Other issues are due to an inconsistent environment, XML application. So once your Setup is correct, there is no need anymore to check console.txt.

Markus

R
Russ Ward
Legend
March 15, 2017

Russ -- That does sound like a nice approach.  I have not used ExtendScript -- just FrameScript.  Do they play well together? Could a FrameScript call out to an ExtendScript or vice versa, do you know?


Shelley,

I don't know much about FrameScript, but my guess is that they should work together. That is, you should be able to call an ExtendScript from within a FrameScript with CallClient (or whatever the FS equivalent is). However, you might want to contact the FrameScript people to see if they support this property first. Maybe it is already there and you don't need ExtendScript.

You might also think about adding some custom behavior to assist your post-processing. Not to encourage scope creep, of course, but you know that if you are retrieving and writing the messaging yourself, you can parse it and modify it along the way. All within the FM scripting. You could send it over a socket connection to some listening agent on another server. You could probably have the script email you whenever anyone screws up. Or, you could just write the stuff to a file like you originally wanted

Russ

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices