Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Svetlana,

I don't believe this works, a native view is orientated in cross tab form and is intended for consumption by people.

A "flat view", is used as a datasource and is used for exporting to text or for a TI process.

They have different features and properties.

For example,  I don't believe it is possible to update a flat views definition to include C levels, instead of excluding them. 

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Steven,

Even it's not a crosstab view but a flat view, it should be possible to save and see the view available as .vue. It'd be in the data tree shown in books side as well:

Best regards,

Hi Svetlana,

I don't believe this works, a native view is orientated in cross tab form and is intended for consumption by people.

A "flat view", is used as a datasource and is used for exporting to text or for a TI process.

They have different features and properties.

For example,  I don't believe it is possible to update a flat views definition to include C levels, instead of excluding them. 

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Svetlana,

The only place you can interact with the additional settings that relate to a flat view is either when you first build it or when you export it.  These can not be edited and saved.

The flat view interface in the Export data is also much easier to interact with and review than viewing the same information in a cross tab (IMO). 

(While I am here.... It would be great if the "Create View" functionality used the same vertical layout as the Export View.  Horizontal layouts are pretty clunky...)

Hi Steven,

Even it's not a crosstab view but a flat view, it should be possible to save and see the view available as .vue. It'd be in the data tree shown in books side as well:

Best regards,

Hi Svetlana,

I don't believe this works, a native view is orientated in cross tab form and is intended for consumption by people.

A "flat view", is used as a datasource and is used for exporting to text or for a TI process.

They have different features and properties.

For example,  I don't believe it is possible to update a flat views definition to include C levels, instead of excluding them. 

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Steven,

Please, log in your idea on !AHA

We'd need to rank that functionality for future implementation.

Thank you!

Hi Svetlana,

The only place you can interact with the additional settings that relate to a flat view is either when you first build it or when you export it.  These can not be edited and saved.

The flat view interface in the Export data is also much easier to interact with and review than viewing the same information in a cross tab (IMO). 

(While I am here.... It would be great if the "Create View" functionality used the same vertical layout as the Export View.  Horizontal layouts are pretty clunky...)

Hi Steven,

Even it's not a crosstab view but a flat view, it should be possible to save and see the view available as .vue. It'd be in the data tree shown in books side as well:

Best regards,

Hi Svetlana,

I don't believe this works, a native view is orientated in cross tab form and is intended for consumption by people.

A "flat view", is used as a datasource and is used for exporting to text or for a TI process.

They have different features and properties.

For example,  I don't believe it is possible to update a flat views definition to include C levels, instead of excluding them. 

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

I'll do this, but I really don't believe this is an "idea".  It's functionality that exists in the legacy product and being able to build an object that you are unable to edit and save seems to be incomplete functionality

Hi Steven,

Please, log in your idea on !AHA

We'd need to rank that functionality for future implementation.

Thank you!

Hi Svetlana,

The only place you can interact with the additional settings that relate to a flat view is either when you first build it or when you export it.  These can not be edited and saved.

The flat view interface in the Export data is also much easier to interact with and review than viewing the same information in a cross tab (IMO). 

(While I am here.... It would be great if the "Create View" functionality used the same vertical layout as the Export View.  Horizontal layouts are pretty clunky...)

Hi Steven,

Even it's not a crosstab view but a flat view, it should be possible to save and see the view available as .vue. It'd be in the data tree shown in books side as well:

Best regards,

Hi Svetlana,

I don't believe this works, a native view is orientated in cross tab form and is intended for consumption by people.

A "flat view", is used as a datasource and is used for exporting to text or for a TI process.

They have different features and properties.

For example,  I don't believe it is possible to update a flat views definition to include C levels, instead of excluding them. 

Hi Steven,

The ability to save the view as a native view had been released in PAW 2.0.99.

That is available in books/reports and in Workbench, so both users - Analysts and Modelers are able to compose the view and save it as a datasource for TI processes.

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnibr2-saving-cube-view-as-native-view

Best regards,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,

Hi Steven,

The cube viewer in PAW allows you to manipulate a flattened view the same way the Architect\Perspectives cube viewer does.  The only real limitation with the PAW cube viewer is that it doesn't display data when the row or column axis has no dimensions.  The view is still completely valid and will be processed by a TI process exactly like a view that was updated from Architect or Perspectives.  You can still access the set editor to modify the current set for each dimension and save changes to the view to TM1.  Saving native views back to TM1 is possible as of PAW 2.0.99.

The fields panel for the cube viewer in PAW books shows the dimensions with a vertical presentation.  I would like to bring a vertical presentation option for the dimensions to the cube viewer in the workbench as well.  I think vertical presentation is generally helpful when working with views with many dimensions.

We could also look into a reusable data export feature to generate a TI process that defines a temporary view for export.  This might compliment our roadmap to make the guided import feature reusable.

Would you feel like the problem is solved if we got the cube viewer to render data when all dimensions were on a single axis (row or column)?

Hi Svetlana,

Thanks for the update, a couple of further comments.

Hopefully this will be early in Q1 as being able to export data as an end-user will be critical for people migrating from the legacy world, especially when you consider the need to go through UAT and so forth with the revised functionality and new releases of PAW generally.

A common use for these flat views is as a source for TI processes.  It is therefore required to be able to update them so you can modify the source for a TI.  You are correct that you can modify the view in the export dialogue but there is no option to commit these change back to the view definition.  Again this is critical for many migrating from the legacy world. 

All the best!

Hi Steven,

You're correct - in our first release of the functionality, we added that for the Workbench Admin/Modeler users, however later the same capability is going to be opened to the analysts in Reports and Analysis in books. We're thinking that that should be configurable as not all the organizations willing to allow the data export. Anyway, it should be available in 2025.  On the tuning the views to be exported as a flat file, if you would click to the Next button (grey button) instead of Export (blue button), you'd see all the opetions to fine tune your export file via the choices available in this wizard, no need to modify the view itself.

Best regards,

Hi,

With the release of PAW 2.0.99 the export as text and flat view creation functionality has been updated.

I'd like to understand if this is viewed as complete by Product Management?

From where we sit there are a couple of significant issues.

1. It is not possible to edit a flat view once created.
2. Creating a flat view is on a workspace, exporting a flat view is on a workbench and as such is Admin only functionality.  Export as text is end-user functionality in the legacy world.  This means that putting the export functionality behind the Admin licence creates a significant issue for well established business processes for those migrating from the legacy world.

TIA for any comments,