Differences

This shows you the differences between two versions of the page.

--- billing:stylesheet [2026/08/18 02:52] – [Running TMSS10LogStatsProcess] Scott Cunliffe
+++ billing:stylesheet [2026/08/18 02:56] (current) – [XML Displays as Unformatted Text] Scott Cunliffe
@@ Line 126: / Line 126: @@
 ===== Troubleshooting =====
-==== XML Displays as Unformatted Text ====
-Check that:
-  * The XML contains an ''xml-stylesheet'' processing instruction.
-  * The stylesheet filename is spelled correctly.
-  * The stylesheet exists at the referenced location.
-  * The Desktop UI or browser has permission to read the stylesheet.
-  * The stylesheet is valid XML.
-  * The stylesheet uses the correct XSLT namespace.
-  * The application supports XSLT processing.
 ==== Stylesheet Cannot Be Found ====
@@ Line 149: / Line 139: @@
   * The billing process is not referencing an old stylesheet location.
-==== Billing Information Is Missing From the Display ====
-The information may exist in the XML but not be selected by the stylesheet.
-Check that:
-  * The expected elements exist in the billing XML.
-  * The stylesheet uses the correct element names.
-  * The ''xsl:for-each'' path matches the XML structure.
-  * The ''xsl:value-of'' expressions match the required fields.
-  * The stylesheet was designed for the current billing XML format.
-Example selection path:
-<code xml>
-<xsl:for-each select="tapetrack_data/item">
-</code>
-==== Billing Values Are Incorrect ====
-The stylesheet does not calculate billing values.
-Check the following billing inputs instead:
-  * The ''.ttstats'' file.
-  * The Customer Description Map.
-  * The Package Map.
-  * The Billing Rules.
-  * The selected billing date range.
-<WRAP important>
-Changing ''tapetrack.xslt'' will not correct an incorrect quantity, unit cost or total stored in the billing XML.
-</WRAP>
-==== Desktop UI Does Not Load the XML ====
-Check that:
-  * The billing XML is complete and valid.
-  * The XML file has not been truncated.
-  * The stylesheet is accessible.
-  * The XML encoding is supported.
-  * The XMLQuickBooks mapping matches the XML elements.
-  * The Desktop UI has permission to read both files.
 ===== Recommended Practices =====