Santosh has identified the correct table in the database for the Project Notebooks.
One thing I thought worth mentioning is that these notebooks are not separate data entries in the database for each update.
Notebooks are stored as an HTML file that is updated each time the Notebook is updated, so checking against the update_date field would identify which notebook has been updated, but when you extract the information it will be a single text block in HTML format, so the other reporting format would need to be able to get the data from this HTML File.
To get a new instance per update period, you would need to create a new Notebook Topic for each reporting period then update that to get individual period update data. This would likely not help what you are trying to achieve, as it would be harder to identify the corrent memo type to export each month.
The "DISCUSSION" table does store information in text format with a timestamp & the name of the user that made the comment, however there does not appear to be a way to delete these comments from within the Primavera application itself & would have to be deleted at the database level if you wanted to remove them. Unfortunately this field is at the activity level & not available for Project level.
Regards,
Steven
Member for
20 years 6 months
Member for20 years7 months
Submitted by Santosh Bhat on Wed, 2020-08-26 08:14
Hi Rodney, Assuming you're tapping directly into the database tables? I'm no expert in this, but I did look inot the P6 database schema, and there is a table called "WBSMEMO" that conaints the EPS/PROJECT/WBS level notebook topics. The columns within this table are:
ColumnsKeyNameTypeDescriptionDefaultPKwbs_memo_idintegerUnique ID FKproj_idintegerFK to PROJECT table - identifies the project FKwbs_idintegerFK to PROJWBS table - identifies the WBS FKmemo_type_idintegerFK to MEMOTYPE table - identifies the notebook topic wbs_memoblobNotebook contents stored as text string update_datedateRefresh audit field of last date updated. Trigger maintained. update_userstring(255)Refresh audit field of last user updated. Trigger maintained. create_datedateRefresh audit field for date record created. Trigger maintained. create_userstring(255)Refresh audit field for user that created the record. Trigger maintained. delete_session_idintegerDeleted by session id. Client maintained. delete_datedateDeleted date. Client maintained.
So if you can read the update_date and create_date fields, you should be able to achieve what you're looking for.
Member for
8 years 1 monthNo problem.
No problem.
Regards,
Steven
Member for
13 years 4 monthsHi Steven, Brilliant, I'll
Hi Steven,
Brilliant, I'll pass your comments over to our DB administrator, thank you so much for that information.
Regards,
Rod
Member for
8 years 1 monthRod,Santosh has identified
Rod,
Santosh has identified the correct table in the database for the Project Notebooks.
One thing I thought worth mentioning is that these notebooks are not separate data entries in the database for each update.
Notebooks are stored as an HTML file that is updated each time the Notebook is updated, so checking against the update_date field would identify which notebook has been updated, but when you extract the information it will be a single text block in HTML format, so the other reporting format would need to be able to get the data from this HTML File.
To get a new instance per update period, you would need to create a new Notebook Topic for each reporting period then update that to get individual period update data. This would likely not help what you are trying to achieve, as it would be harder to identify the corrent memo type to export each month.
The "DISCUSSION" table does store information in text format with a timestamp & the name of the user that made the comment, however there does not appear to be a way to delete these comments from within the Primavera application itself & would have to be deleted at the database level if you wanted to remove them. Unfortunately this field is at the activity level & not available for Project level.
Regards,
Steven
Member for
20 years 6 monthsHi Rodney, Assuming you're
Hi Rodney, Assuming you're tapping directly into the database tables? I'm no expert in this, but I did look inot the P6 database schema, and there is a table called "WBSMEMO" that conaints the EPS/PROJECT/WBS level notebook topics. The columns within this table are:
ColumnsKeyNameTypeDescriptionDefaultPKwbs_memo_idintegerUnique ID FKproj_idintegerFK to PROJECT table - identifies the project FKwbs_idintegerFK to PROJWBS table - identifies the WBS FKmemo_type_idintegerFK to MEMOTYPE table - identifies the notebook topic wbs_memoblobNotebook contents stored as text string update_datedateRefresh audit field of last date updated. Trigger maintained. update_userstring(255)Refresh audit field of last user updated. Trigger maintained. create_datedateRefresh audit field for date record created. Trigger maintained. create_userstring(255)Refresh audit field for user that created the record. Trigger maintained. delete_session_idintegerDeleted by session id. Client maintained. delete_datedateDeleted date. Client maintained.
So if you can read the update_date and create_date fields, you should be able to achieve what you're looking for.