To register for the forums, please contact your Digital-Clay representative.
Document Anomaly
Document Anomaly
Following the recent update to 9.0.10, 2 computers have exhibited the following:
When we right click on 1 or more records in a list so as to perform Generate Document (output based on doc. template), when a particular template is chosen, Clay station closes completely.
Outputting the same template through print/save document seems to function normally.
On the other computers, the document template shortcut via Generate Document seems to work successfully.
Any suggestions?
When we right click on 1 or more records in a list so as to perform Generate Document (output based on doc. template), when a particular template is chosen, Clay station closes completely.
Outputting the same template through print/save document seems to function normally.
On the other computers, the document template shortcut via Generate Document seems to work successfully.
Any suggestions?
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Document Anomaly
What is this "Generate Document" ...is it a custom Template Action you guys added? If so then try to perform the same action with identical settings from Print/Save and see if that causes a crash.
In other words, perhaps it is a combination of the copy of the template on that specific computer plus the specific settings in the action.
In other words, perhaps it is a combination of the copy of the template on that specific computer plus the specific settings in the action.
Re: Document Anomaly
Yes, Generate Document...is a custom Template Action.
Yes, as I said, when we tried to output the same template through print/save document, it seems to function normally.
As all of our computers use templates from the same location on a network drive, there is no "copy of the template on that specific computer" as far as I know.
Suggestions?
Yes, as I said, when we tried to output the same template through print/save document, it seems to function normally.
As all of our computers use templates from the same location on a network drive, there is no "copy of the template on that specific computer" as far as I know.
Suggestions?
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Document Anomaly
Yes, but I mentioned the action settings. By this I mean how you configured the action to run, including the output format, the automation/auto-attachment settings if any, etc. When you run it via the normal Print/Save and use identical settings as in the action, does it crash?
I think I will need a screenshot of the template action editor to see how it is configured, including template action automation settings if any.
I think I will need a screenshot of the template action editor to see how it is configured, including template action automation settings if any.
Re: Document Anomaly
With identical settings in print/save, it does not crash.
- Attachments
-
- template action full record 121104.gif (52.34 KiB) Viewed 26041 times
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Document Anomaly
I can't reproduce it on my end so far, and you did say that it is inconsistent per machine... but I noticed one thing in your screenshot: The extension of the template file seems to be "HTMLDCTM..." which sounds like a mistake. Please go to your template folder and tell me what the exact filename+extension is for all template files beginning with "Entity Full Record".
P.S. Looks like there will be a release very soon so it is recommended we work this out quickly before the release.
P.S. Looks like there will be a release very soon so it is recommended we work this out quickly before the release.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Document Anomaly
While you are at it, you should attach the template file here as well so that I can try to reproduce the problem.
Also, double check in the Tools/Options for both the machine where it works and the machine where it doesn't, and make sure they are both using the same Template folder in the advanced settings.
Also, double check in the Tools/Options for both the machine where it works and the machine where it doesn't, and make sure they are both using the same Template folder in the advanced settings.
Re: Document Anomaly
The are all located in K:\DigitalClay\Templates.
The file is therefore K:\DigitalClay\Templates\Entity Full Record.stm
Interestingly enough, I tried using Generate Document to output the template for 1, 3 and then 4 records on a computer where it works and watched the Templates folder during the process. I notice that 3 additional files have been created in addition to the original (Entity Full Record.stm):
Entity Full Record.stm.htmlEntity Full Record.stm
Entity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm
Entity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm
Bizarre?
Both computers have the same folder listed for templates.
The file is therefore K:\DigitalClay\Templates\Entity Full Record.stm
Interestingly enough, I tried using Generate Document to output the template for 1, 3 and then 4 records on a computer where it works and watched the Templates folder during the process. I notice that 3 additional files have been created in addition to the original (Entity Full Record.stm):
Entity Full Record.stm.htmlEntity Full Record.stm
Entity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm
Entity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm.htmlEntity Full Record.stm
Bizarre?
Both computers have the same folder listed for templates.
- Attachments
-
[The extension html has been deactivated and can no longer be displayed.]
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Document Anomaly
Success. We found the crash and the cause. In the meantime, you should do two things:
1. Delete all the bizarre/duplicate template files except the orginal (Entity Full Record.stm.html)
2. Open the template action in the editor and select the remaining correct template, then press OK so that it saves the action.
1. Delete all the bizarre/duplicate template files except the orginal (Entity Full Record.stm.html)
2. Open the template action in the editor and select the remaining correct template, then press OK so that it saves the action.