Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
My application is asking every time 'SAVE AS' whenever i click 'save' button.
For all i know it is because of section access.
How can i avoid save as pop up.
Regards,
Nihhal.
I know these behavior since years and it's a kind of security measure which occured if the app wasn't reloaded before saving them and if there are any gaps between the fields from section application and section access.
For example you have a field region within your datamodel which is linked to the section access and one or more values are missing respectively NULL or you have values within the region which are not included within the section access then the "save as" dialog appeared.
There are further features so that such saving without a reload meant that no access per access point possible is. Unfortunately is the technical documentation from the section access quite small so that the question "why" couldn't be answered.
Now you could decide to live with these features or you made the efforts to remove the gaps by using a where-condition on these data which aren't included within the section access and by missing values have a look on these links:
replace null values with "missing"
Filling Default Values Using Mapping | Qlikview Cookbook
- Marcus
Hi Nihhal,
do you mean, when using File > Save? Or something else?
Andy
I know these behavior since years and it's a kind of security measure which occured if the app wasn't reloaded before saving them and if there are any gaps between the fields from section application and section access.
For example you have a field region within your datamodel which is linked to the section access and one or more values are missing respectively NULL or you have values within the region which are not included within the section access then the "save as" dialog appeared.
There are further features so that such saving without a reload meant that no access per access point possible is. Unfortunately is the technical documentation from the section access quite small so that the question "why" couldn't be answered.
Now you could decide to live with these features or you made the efforts to remove the gaps by using a where-condition on these data which aren't included within the section access and by missing values have a look on these links:
replace null values with "missing"
Filling Default Values Using Mapping | Qlikview Cookbook
- Marcus
Yes or save icon.
Thank you Sommer.