<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Philip Las Gourgues's Activities</title><link>https://communities.bentley.com/members/68156003_2d00_2d39_2d00_495d_2d00_951c_2d00_30534bfdf5f3</link><description>Philip Las Gourgues's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Permissions to change workflow applied to folder</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/238865/permissions-to-change-workflow-applied-to-folder</link><pubDate>Wed, 30 Nov 2022 07:02:40 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ce5d8292-63c3-4487-83c1-930cfaa975d3</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;HI all,&lt;/p&gt;
&lt;p&gt;Is there a way to restrict user permissions so they can change workflow states as per the access control configured on the folder but prevent them from changing the whole workflow applied to that folder? As far as I can tell the two permissions are bundled together and users changing the whole workflow at the folder level can be catastrophic.&lt;/p&gt;
&lt;p&gt;Thanks all.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question II</title><link>https://communities.bentley.com/achievements/cd3cd235-25c1-476e-bb88-33a5705ca45a</link><pubDate>Thu, 14 Apr 2022 05:51:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:0bbf6ad7-8323-4553-8fd1-744289c6eb38</guid><dc:creator /><description>Ask 10 questions in a forum.</description></item><item><title>export-pwaccesscontroltoexcel and 365 Sensitivity Label</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-powershell-extensions-forum/228430/export-pwaccesscontroltoexcel-and-365-sensitivity-label</link><pubDate>Thu, 14 Apr 2022 05:48:43 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e4524fa7-fd11-4f53-995c-df5e72785be5</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Our organisation has recently started using the Office 365 Sensitivity labelling and mandate the application of a label prior to saving a document or sending an Outlook email. This appears to have blocked the Powershell function from being able to access the spreadsheet when outputting access control and by the time a label is picked from the dialogue that pops up it seems like the function has timed out. The process completes but the spreadsheet is empty apart from the default headers.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve tried the switches to ignore and silently continue on errors but they don&amp;#39;t seem to help. Has anyone else come across this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Module to create connected groups</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-powershell-extensions-forum/223343/module-to-create-connected-groups</link><pubDate>Mon, 13 Dec 2021 06:01:33 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:188e4af9-d5d0-4b04-9490-d59f8531d3b6</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;HI all,&lt;/p&gt;
&lt;p&gt;We&amp;#39;re currently working on an automated project setup application and are utilising the&amp;nbsp;Add-PWConnectedProject module to create the project in the IMS portal but need a way to create the connected groups that will sync with their corresponding PW groups. Does anyone know if such a module exists or if there&amp;#39;s an alternative way to do scripted creation of IMS groups?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Import-PWDocumentsBySpreadsheet error</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-powershell-extensions-forum/192888/import-pwdocumentsbyspreadsheet-error</link><pubDate>Mon, 24 Feb 2020 06:58:36 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:7eeedb8d-d786-4559-9cb8-7f47fc6f9fa9</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;pwps_dab version 1.18.2.0&lt;/p&gt;
&lt;p&gt;ProjectWise version&amp;nbsp;10.00.03.140&lt;/p&gt;
&lt;p&gt;I&amp;#39;m attempting to use&amp;nbsp;Import-PWDocumentsBySpreadsheet to create some new documents on a datasource and populate their attributes.&amp;nbsp; I&amp;#39;ve started by creating the spreadsheet using Export-PWDocuments with the -ExportMetadata switch then modified the created file as required.&lt;/p&gt;
&lt;p&gt;Unfortunately I keep getting the below error even if I just run a straight export/import of the spreadsheet without modifying. Has anyone come across this error before and any ideas on how to resolve it?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;WARNING: Length cannot be less than zero.&lt;/em&gt;&lt;br /&gt;&lt;em&gt;Parameter name: length&lt;/em&gt;&lt;br /&gt;&lt;em&gt;WARNING: at System.String.Substring(Int32 startIndex, Int32 length)&lt;/em&gt;&lt;br /&gt;&lt;em&gt; at PWPS_DAB.ImportExport.UpdatePWDatesAndUsers(Int32 iProjectId, Int32 iDocumentId, Int32 iCreatorId, Int32 iUpdaterId, Int32 iFileUpdaterId, String sCreateDate, String sUpdateDate, String &lt;/em&gt;&lt;br /&gt;&lt;em&gt;sFileUpdateDate, PSCmdlet cmdlet)&lt;/em&gt;&lt;br /&gt;&lt;em&gt; at PWPS_DAB.ImportExport.ImportFromSpreadsheet(String sInputSpreadsheet, String sTargetFolderPath, Int32 iProjectId, Int32 iStorageId, Int32 iEnvironmentId, Int32 iWorkflowId, Boolean bCrea&lt;/em&gt;&lt;br /&gt;&lt;em&gt;teNewVersionIfExists, Boolean bJustUpdateAttributes, Boolean bSkipAuditTrail, Boolean bWriteBackLinks, Boolean bDeleteFilesOnImport, Boolean bCreateMissingFiles, PSCmdlet cmdlet)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Clear-PWWorkflowByFolderPath not functioning as expected</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-powershell-extensions-forum/185733/clear-pwworkflowbyfolderpath-not-functioning-as-expected</link><pubDate>Wed, 18 Sep 2019 02:02:31 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a5a1ae42-bcb3-4300-af68-162cd02bcf4d</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;I&amp;#39;m running ProjectWise 10.00.03.140 and PWPS_DAB 1.12.3.0.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When I run the below to attempt to clear the workflow from a nested folder structure it returns &amp;quot;WARNING: Folder &amp;#39;XXXX&amp;#39; not found&amp;quot; for every folder ID in the path.&lt;/p&gt;
&lt;p&gt;$folders=Get-PWFolders -FolderPath &amp;#39;MET502\CAD&amp;#39;&lt;br /&gt;foreach ($folder in $folders) {Clear-PWWorkflowByFolderPath $folder.ProjectID}&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If I manually enter the command as below for a single folder it works as expected even though the test folder is exactly the same ID as one not found above.&lt;/p&gt;
&lt;p&gt;Clear-PWWorkflowByFolderPath -FolderID XXXX&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Any suggestions would be greatly appreciated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Oracle query with IS NULL and CASE WHEN</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/184575/oracle-query-with-is-null-and-case-when</link><pubDate>Tue, 27 Aug 2019 00:28:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:994ab70d-4324-41cb-ae8f-2ace07b78b9f</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We&amp;#39;re running ProjectWise 10.00.03.140 on an Oracle database and I&amp;#39;m having some issues with Oracle functions not working as expected.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m attempting to write a query to parse a series of attributes and select the last non-null one to populate current drawing approvers and current revisions.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When the main query failed I wrote the simplified test case below which also fails. I did manage to get it to work in another environment by replacing IS NULL with = &amp;#39; &amp;#39; but this seems to be dependent on the attribute being referenced as it doesn&amp;#39;t work for the B6_DESIGNED case below.&lt;/p&gt;
&lt;p&gt;select&amp;nbsp;case&amp;nbsp;when&amp;nbsp;&amp;#39;$EDIT#B6_DESIGNED$&amp;#39;&amp;nbsp;is&amp;nbsp;null&amp;nbsp;then &amp;#39;BLANK&amp;#39;&amp;nbsp;else &amp;#39;NOT BLANK&amp;#39;&amp;nbsp;end&amp;nbsp;from DUAL&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve also had an issue with running into the 1024 character limit for queries. Is there any way around this without splitting part of the query into an interim attribute? I&amp;#39;ve considered stored procedures but I&amp;#39;m concerned this may not be allowed when we migrate to a Bentley cloud hosted solution in the future.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The full query I&amp;#39;m attempting to run is shown below (I&amp;#39;ve had to truncate the last couple of revisions to get it under the 1024 character limit). A6_DESIGNED to F6_DESIGNED are VARCHAR attributes, SIGNERS is a lookup environment and INITIAL_SURNAME and INITIALS are both VARCHAR attributes in the SIGNERS environment.&lt;/p&gt;
&lt;p&gt;select case when &amp;#39;$EDIT#F6_DESIGNED$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;select case when &amp;#39;$EDIT#E6_DESIGNED$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#D6_DESIGNED$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#C6_DESIGNED$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#B6_DESIGNED$&amp;#39; = &amp;#39; &amp;#39; then (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#A6_DESIGNED$&amp;#39;)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#B6_DESIGNED$&amp;#39;) end from DUAL) &lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#C6_DESIGNED$&amp;#39;) end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#D6_DESIGNED$&amp;#39;) end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#E6_DESIGNED$&amp;#39;) end from DUAL)&lt;br /&gt;else (select INITIAL_SURNAME from SIGNERS where INITIALS like &amp;#39;$EDIT#F6_DESIGNED$&amp;#39;) end from DUAL&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The below query works as required in a different environment. Obviously it&amp;#39;s not referencing another environment via lookup so that may be the issue.&lt;/p&gt;
&lt;p&gt;select case when &amp;#39;$EDIT#REV10$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;select case when &amp;#39;$EDIT#REV9$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV8$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV7$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV6$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV5$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV4$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV3$&amp;#39; = &amp;#39; &amp;#39; then (&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;select case when &amp;#39;$EDIT#REV2$&amp;#39; = &amp;#39; &amp;#39; then (select &amp;#39;$EDIT#REV1$&amp;#39; from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV2$&amp;#39; end from DUAL) &lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV3$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV4$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV5$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV6$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV7$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV8$&amp;#39; end from DUAL)&lt;br /&gt; &lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;else &amp;#39;$EDIT#REV9$&amp;#39; end from DUAL)&lt;br /&gt;else &amp;#39;$EDIT#REV10$&amp;#39; end from DUAL&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks very much.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Version formatting</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/150391/version-formatting</link><pubDate>Tue, 03 Apr 2018 05:20:39 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:e950feaf-078e-4163-9142-9f19a9db5cce</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Hi All,&lt;/p&gt;
&lt;p&gt;I suspect the answer is going to be &amp;quot;use the rules engine&amp;quot; but I thought I&amp;#39;d check just in case. We&amp;#39;re currently working on a rules engine deployment but it&amp;#39;s still a little way off and a new project has a simple requirement.&lt;/p&gt;
&lt;p&gt;What I&amp;quot;m trying to do is specify the version format for new documents, new version created within ProjectWise Explorer and new versions created by drag and drop of a file with the same name.&lt;/p&gt;
&lt;p&gt;The required version format for the project is a three digit number with leading zeros (001, 002, 003....). I can get this working fine for the latter case just by specifying a %03d version string for document creation conflicts but I can&amp;#39;t find a similar option for the initial version or for versions created through PWE.&lt;/p&gt;
&lt;p&gt;Any assistance would be much appreciated.&lt;/p&gt;
&lt;p&gt;We&amp;#39;re running 08.11.11.590 but are in the final stages of testing prior to a Connect Edition roll out. It&amp;#39;s an internally hosted system running on an Oracle database.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question I</title><link>https://communities.bentley.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09</link><pubDate>Mon, 19 Feb 2018 01:49:05 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ea53b9f4-18e2-47a7-9401-f1cff8e57c92</guid><dc:creator /><description>Ask a question in a forum.</description></item><item><title>Reference document path during document creation</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/147138/reference-document-path-during-document-creation</link><pubDate>Mon, 19 Feb 2018 07:02:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:8ea70106-eb79-4c95-a6be-5b9ae36fd144</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;I recall seeing a similar topic some time ago but I can&amp;#39;t find it now I&amp;#39;m searching again. I want to use the location a document is being created in to determine the default values of the document code.&lt;/p&gt;
&lt;p&gt;For example the document path might be:&lt;/p&gt;
&lt;p&gt;..\XXX999\001 Example Area\03 CAD\08 Services\01 Drawings\&lt;/p&gt;
&lt;p&gt;The area code &amp;quot;001&amp;quot; in the path above forms part of the document code for the document being created in the &amp;quot;01 Drawings&amp;quot; folder. The list of area codes is populated using a lookup table and I want to reference the document path to determine the default value. Trouble is from my recollection and from the results of my testing you can&amp;#39;t reference any document properties until the document has been created. Sort of a catch 22. Is anyone aware of a workaround for this issue? I also want to similarly reference the &amp;quot;08 Services&amp;quot; to populate the drawing discipline so using sub-projects isn&amp;#39;t an ideal solution.&lt;/p&gt;
&lt;p&gt;Thanks in advance.&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ProjectWise document checkout without DMS directories</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/107794/projectwise-document-checkout-without-dms-directories</link><pubDate>Wed, 10 Jun 2015 08:25:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:b4e5ec48-55a7-49bd-b31a-09056a4e5f23</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I was wondering if it&amp;#39;s possible to set documents to be checked out into their specified Working Directory without going into a numbered DMS sub-directory. A project I&amp;#39;m administering requires the Revit model files to be checked out of ProjectWise into a particular directory and it is strongly preferred they don&amp;#39;t go into a numbered DMS sub-directory within this area.&lt;/p&gt;
&lt;p&gt;Thanks in advance,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Linking ProjectWise Document Attributes</title><link>https://communities.bentley.com/products/projectwise/f/projectwise-di-forum/107390/linking-projectwise-document-attributes</link><pubDate>Mon, 25 May 2015 03:53:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:cb665274-d680-4cd8-ab73-e3e1c2737ee0</guid><dc:creator>Philip Las Gourgues</dc:creator><description>&lt;p&gt;I have an attribute used in the definition of my document code. It&amp;#39;s obtained from a pull down list for discipline and adds a single letter to the document code (S - Structural, C - Civil etc). Later in the document attributes which are linked to a Microstation tag set I want to set an attribute to &amp;quot;STRUCTURAL&amp;quot; if S was chosen in the document code, &amp;quot;CIVIL&amp;quot; if C was chosen in the document code etc. Is there an easy way to do this? We&amp;#39;re running on an Oracle database.&lt;/p&gt;
&lt;p&gt;Thanks in advance,&lt;/p&gt;
&lt;p&gt;Philip Las Gourgues&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>