Product specifications for handling "0" data when exporting Planning data to a CSV file using DI
What are the product specifications for handling "0" data when exporting Planning data to a CSV file using Data Integration?
By setting the application category to "Data Target" and the type to "Data Export to file," you can output Planning data to a specified CSV file. However, is it correct to say that stored data explicitly entered as "0" in Essbase (i.e., not null or #Missing) will not be exported to the CSV file?
Tagged:
0