Jim Turner's Activities

[Web services gateway] Get document path

Oto — Thu, 28 Feb 2019 14:28:46 GMT

How to retrieve document path using Projectwise web services gateway?

Reprojection Settings - Display Errors to Message Center

Oto — Fri, 18 Jan 2019 10:20:28 GMT

According to this wiki https://communities.bentley.com/products/microstation/w/microstation__wiki/8950/reprojection-setting there should be option to display error messages when using reprojection.

I do not see such setting.

Export-PWDocuments without non-admin right?

Björn Johansson — Fri, 07 Feb 2020 10:07:23 GMT

Cmdlet Export-PWDocuments (and similar cmdlets for exporting and reading docs) should be accessible for report-only logins (users running the cmdlets by the Non-Admin). Why do you need have admin rights to export files in PowerShell?

Enhancement request: saved search option for Get-PWDocumentsBySearchWithReturnColumns

Jim Turner — Tue, 28 Jan 2020 14:29:49 GMT

The cmdlet Get-PWDocumentsBySearchWithReturnColumns is much faster and much more performant to retrieve (known) attribute values than the Get-PWDocumentsBySearch -GetAttributes method. As such when retrieving large numbers of documents it becomes the de facto standard method.

Can the same search options be added to the Get-PWDocumentsBySearchWithReturnColumns cmdlet as available to the Get-PWDocumentsBySearch cmdlet?

Specifically please add the saved search (-SearchName <string>) and spatial parameters (-LatitudeMin <double> etc.) to Get-PWDocumentsBySearchWithReturnColumns.

Geographic coordinate system missing

Eurico Inacio — Sat, 24 Mar 2018 15:50:24 GMT

Hello,

I'm currently working in a big railway project that uses a bespoke GCS.

I was following a forum post that explaining how to create a transformation. In the process the seed file "UserOverrideGeodeticTransformSeed.asc" needed to be altered.

The heading of the file contain the following text:

"# In case of absolute necessity it is possible to override the list or
# order of the grid shift files for a specific datum transformation.
# This should only be done if no other solution is available.
# Bentley Systems would be glad to introduce new files directly
# referenced by the built-in system dictionary as part of a refresh to
# its software. Contact Bentley system through the normal support channel."

As you can imagine this new GCS is a big headache with all the legacy data.

Is there anyone in the position to help?

Thank you in advance for your time.

Regards,

Eurico

ProjectWise WSG: how to run a spatial query

Jim Turner — Wed, 27 Mar 2019 15:32:09 GMT

According to the WSG policies (Policies/PolicyAssertion/Persistence.SpatialQueries) it states that spatial queries are supported, along with the polygon type and the operator 'Intersects'.

The WSG documentation also describes the use of WKT geometry and use of the intersects operation. I have tried to build a query but I can't find anything that works in the place of the [***] string:

Repositories/[PWREP]/PW_WSG/Document?$filter=geometry'POLYGON((-1.24933 52.1257,-1.24398 52.1256,-1.24392 52.1296,-1.24926 52.1296,-1.24933 52.1257))'+intersects+[***]

In practice how does one use spatial queries? I'm using API v2.5.

Let me Help You

Tue, 12 Mar 2019 02:56:00 GMT

Answer a question that is verified as helpful or correct.

New-PWDocumentVersion - database deadlock error?

Jim Turner — Tue, 22 Jan 2019 15:19:23 GMT

I have a script to synchronize files in a server folder with documents in a ProjectWise folder. I have several thousands of documents to sync so I have 'powershelled' the task.

One of my commands is to create a new document version:

Get-PWDocumentsBySearch -FolderPath $pwfolder -FileName $theFile | New-PWDocumentVersion -VersionString $verString | Out-Null

This will happily run for long periods of time, and then fall over for no apparent reason:

New-PWDocumentVersion : Error changing document 'FILENAME' to new
version. Error creating new version of document.At SCRIPTNAME1:548 char:97
+ ... e $theFile | New-PWDocumentVersion -VersionString $verString | Out-N ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Version:String) [New-PWDocumentVersion], Exception
+ FullyQualifiedErrorId : ErrorID: Database transaction deadlock error.,PWPS_DAB.NewPWDocumentVersion

What is a database transaction deadlock error and how to prevent it? For the record, the $verString is set to "P02" and the previous version is "P01".

Thanks for any help.

New-PWDocumentVersion Error/Exception Handling

Jim Turner — Tue, 23 Oct 2018 13:09:02 GMT

I am using New-PWDocumentVersion cmdlet as part of a script to synchronize DGN files on a server drive with the respective holdings on ProjectWise.

To deal with problems and exceptions in my script I have the following set:

$ErrorActionPreference = "Stop"
$WarningPreference = "Inquire"

The basic process involves creating a new version and uploading the PW document if the server file is more up-to-date than the PW file. I create new versions like such and then update the file:

Get-PWDocumentsBySearch -FolderPath $pwfolder -FileName $theFile | New-PWDocumentVersion -VersionString $verString | Out-Null

Get-PWDocumentsBySearch -FolderPath $pwfolder -FileName $theFile | Update-PWDocumentFile -NewFilePathName $newfile | Out-Null

For an unexplained reason the New-PWDocumentVersion cmdlet is failing, with the following text written to screen:

Error changing document '\path\xxx.dgn' to new version

The reason for the error is not clear and I am so far unable to recreate it consistently. Most distressingly however, because the error is not raised as a normal Powershell exception, the script blithely continues and actually overwrites the document of the previous version.

Please can the cmdlet be updated to raise exceptions correctly? Actually I've also noted this on other cmdlets too, including Update-PWDocumentAttributes, therefore this request can be opened up to all cmdlets.

Ask A Question I

Tue, 23 Oct 2018 01:58:19 GMT

Ask a question in a forum.