I have noticed and a customer is having a problem with the hash sign (#) now ending
the file name of the generated NWC file. When doing an export from an
application, this hash sign is not added. The problem is that search sets do
not work when the customer receives a new NWC export and the file name is
without the hash!?
I have done some tests here and found that if I add the hash to the end of the exported files
name, I can get the search sets to work. Could you explain the reason for the
hash in generated NWC files and not in the exported files in the 2012 version.
Might I ask what workflow you are following here? NWC files generated by export and NWC files generated as cache files are not really guaranteed interchangeable like you describe. They can work, but you can get subtle differences when dealing with things like relative paths. Generally one would always use export NWC if using an exporter, and always use cache NWC files if using a file loader.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!