Trying to bulk import our Alarm Help information from our Alarm Management meetings into DeltaV. I'm running into an issue because some of our "Recommended Actions" are more than 255 characters and the Bulk Import bombs out. Anyone else have this issue and is there a work around (other than leaving those particular ones > 255 characters out of the bulk import file and manually copying them in)?
The import results dialog will issue a warning when a help text fields exceeds 500 characters and make no changes to any of the fields of that particular module. The module containing the lengthy help entry gets flagged with an error, but bulk edit should without bombing proceed to import the next module in the import file. Hand entering alarm help won't allow you to get more than 500 chars either, so it will be necessary to do some editing. Assuming you have the text in Excel, you may want to enable Excel bulk edit support (Open the BulkEdit_Support file in the DVData\BulkEdit folder from Excel) so that you can use the Excel LEN function to find the rows (modules) that have help text entries that exceed 500 chars.
In reply to Kim Van Camp:
Thanks for the response Kim, but I'm seeing something different. Let me provide a little more information to be helpful. We are using v11.3. I am using an ODBC source linked to my Excel workbook to do the bulk edits. When doing the import, I am seeing 1 of either 2 errors. 1 of the errors happens during the creation of the "Temporary Script File" ODBCScript#.fhx (before it even starts trying to import the modules). In the "Import results" dialog box, it just gets to the first line "FILE: ODBCScript#.fhx opened." Then a small window pops up with the message "Data truncated." Only option is to click "OK". That leads to another small pop up window with the message "Error opening file" and the only option is to click "OK". At that point the entire Bulk Import has been cancelled and gone away. The other error I've seen is similar - it happens at the same time at the very beginning of the Import during the ""Temporary Script File" ODBCScript#.fhx " creation. The first line in the "Import results" dialog box also says "FILE: ODBCScript#.fhx opened." And then a slightly larger window pops up with the message "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." Again the only option is to click "OK". That leads to the same small pop up window with the message "Error opening file" and the only option is to click "OK". At that point the entire Bulk Import has been cancelled and gone away.
This is happening with just more than 255 characters. I've changed the larger fields to be just 255 characters and the bulk import proceeds just fine. I go to 256 characters in that field and I get 1 of the 2 error situations described above. I can manually paste the contents of the field in that are >255 characters, but that will be time consuming. Hadn't tried anything over 500 characters so that's good to know about that limit.
In reply to Shannon Jistel:
sorry - using v11.3.1
Have you tried importing from a flat CSV file, rather than through ODBC? If it's a problem with the ODBC code in the import, you may at least be able to get around it in the short term that way.
In reply to Brian Atkinson:
Thanks, Brian! I tried saving that worksheet through the DeltaV Bulk Edit Add-in by using the Save Data File menu option. That saved the worksheet as a .txt tab delimited text file. I specified that .txt file on the Bulk Import instead of my ODBC source and that was able to import everything just fine! So that will work. Thanks again!