After importing articles from one project into another, the Listen feature does not read variable values.
This happens because the variables referenced in the imported articles did not exist in the destination project at the time of import, so the content could not link to them correctly. You can prevent this by creating all required variables in the destination project before importing any content.
Before you begin
Confirm you have Owner or Admin access in the destination project — you need this to create variables.
Have a list of all variables used in the articles you plan to import. You can review these in the source project under Settings > Variables.
Fix the Listen feature not reading variable values
In the destination project, navigate to Settings > Variables.
Select New variable and recreate each variable from the source project, using the same name and value.
Repeat until all required variables exist in the destination project.
Import the articles or category structure into the destination project.
Open each imported article in the editor and confirm the variable placeholders are rendering the correct values.
Select Publish for each article.
The Listen feature can now read the variable values as expected.
Verify the fix
Open a published article that contains variables.
Select the Listen icon in the article toolbar.
Confirm the audio reads out the variable values and not the placeholder syntax.
Note:
If the Listen feature still does not read variable values in an article imported before creating the variables, unpublish the article, open it in the editor, and republish it. This forces the system to re-evaluate the variable references.
If the Listen feature still does not read variable values in an article imported before creating the variables, unpublish the article, open it in the editor, and republish it. This forces the system to re-evaluate the variable references.
Why this happens
When articles are imported, Document360 checks whether the variables referenced in the content already exist in the destination project. If they do not, the imported content cannot form the correct association between the variable placeholders and the variable definitions. Even if the variables are created afterward, the previously imported articles may retain broken references. The Listen feature relies on these associations to resolve and read variable values aloud, so articles imported before the variables were created may not work correctly until republished.
FAQ
Does this affect all articles in the import or only some?
It affects only articles that contain variable references. Articles without variables are not impacted.
Do I need to republish every imported article to fix the issue?
Only articles that were imported before the variables were created need to be republished. Articles imported after the variables exist are linked correctly at the time of import.
Will the variable values appear correctly in the editor even if Listen does not read them?
Sometimes. The editor may display the resolved variable value visually, but the Listen feature may still fail to read it if the underlying reference was not established correctly during import.
What if I do not know which variables are used in the articles I plan to import?
Review the source project under Settings > Variables to see all variables defined there. Cross-check these against the articles you intend to import before starting.
I followed the steps and republished, but Listen still skips the variable values. What next?
Contact Document360 support with the affected article URL and variable names. Include the order in which the import and variable creation were performed.