Differences

This shows you the differences between two versions of the page.

--- versago3:dataview_display [2022/09/14 15:49]
dlee [Images in Data Views]
+++ versago3:dataview_display [2024/03/14 14:16] (current)
dlee [Field Display]
@@ Line 11: / Line 11: @@
   * **Localization** is used to adjust the formatting of date, datetime, and currency __types__.
   * **File Name** is only accessible when the data type of the column is binary, blob, or varbinary .  See **Note 1** below.
+<WRAP center round info 80%>
+Users will be able to sort by clicking column heading. Multiple column can be sorted by using the CTRL key
+</WRAP>
 **Note 1**
@@ Line 22: / Line 26: @@
   * **Database Source Files** are identified by reference to specific records in a database.  The information provided below refers to files uploaded via a Versago form.
   * The data is found in a table named "TWBS_VGO_FormAttachments".  This table is found in the database where the data captured in the form is stored.
-    * Two values are required from the record: FileName and FileContent.  __FileContent__ is the binary data that will be converted for download.  __FileName__ is used as the reference to the binary data.
+    * Two values are required from the record: FileName and FileContent.  __FileContent__ is the binary data that will be converted for download.  __FileName__ contains the file name of the binary.
-    * When the data type of the column is binary, blob, or varbinary the __File Name__ field for the FileContent row presents a drop-down list of fields from the report query.  Select the column name that contains the associated file name.
+    * The Display Type of __FileContent__ should be set to File
-    * It is not necessary to display the __FileName__ value in the report, but showing the user the name of the file is typically very helpful.
+    * It is not necessary to display the __FileName__ value in the report, but showing the name of the file is typically very helpful.
 The **files in a database** approach does require that the __FileContent__ value is not NULL.  As it is very possible that a report row will not have a corresponding report to download, use the following SQ.  Setting FileContent to 0 when the database value is NULL allows the report to execute without errors.
@@ Line 33: / Line 37: @@
 In both cases, keep in mind that any user that has access to the report can download any file listed in the report. If certain files should be available to certain group(s) of users, different reports may be needed.
+<WRAP center round info 80%>
+Video regarding files and Data Views
+</WRAP>
 ====Highlights====
@@ Line 68: / Line 76: @@
 Images are held in the folder C:\Program Files(x86)\TWBS\Versago\WebApp\SiteImages.
-The images must also be registered in the Versago common database in the versago_image_files table.  A Bizweaver workflow is available to assist with this process.  Images can also be registered manually as described elsewhere in this page.
-====Sample SQL Using Images====
-This example displays a list of production orders with an image of the finished product.
-  * The database for "vgoCommon" may need to be changed for your installation.
-  * "isnull(t1.filepath,'\SiteImages\NoImage_45.png')" assumes you have an image to be displayed when an actual image is not available.
-  * Use either "45" or "65" in the selection.  45 is used in this example.  The other sizes (for the other thumbnail, image rollover and image click) are determined automatically by Versago.
-<code SQL>
-select
-t0.ItemCode, t1.ItemName, isnull(t2.filepath,'\SiteImages\NoImage_45.png') as [ImagePath], t0.DueDate, t0.Status, t0.DocEntry, t0.DocNum
-from OWOR t0
-inner join OITM t1 on t0.ItemCode = t1.ItemCode
-left join [vgoCommon].dbo.[versago_image_files] t2 on t0.ItemCode = t2.IntersectionID collate database_default
-where t0.Status in ('R','P')
-AND isnull(t2.filepath,'\SiteImages\NoImage_45.png') like '%45%'
-</code>
-====Register Images Using Bizweaver====
-In most cases, using a Bizweaver workflow will be the quickest and easiest way to register images for use with Versago.  A standard workflow named "Versago Image Loader" is available from Third Wave as a download from [[https://portal.twbs.com]] (login required).  Following are the steps to use the workflow.
-  * Create the four sizes of each image as noted above.  There are a number of applications that can assist with this process.  One that Third Wave has used with good success is __FastStone Image Resizer__ (www.FastStone.org).
-<WRAP center round tip 80%>
-The Bizweaver process provided by Third Wave assumes that the file name is structured as ID_Size.  As an example for image A00001, the file names will be A00001_45, A00001_65, A00001_250, and A00001_1024.
-Further, the "ID" is used to map to a value in the Versago report.  In the previous example, "A00001" will map to an item number in SAP Business One that is included in the report.
-</WRAP>
-    * Place the files in a Windows folder that can be accessed by Bizweaver.
-  * Open the Bizweaver workflow.  The steps will appear as shown in the following image.
-{{ :versago:versago_image_loader_1.png?800 |Image Loader Overview}}
-    * Set the variable __SourceFilePath__ in the Variables_Init (as shown in yellow below) step to folder path from the previous step.
-{{ :versago:versago_image_loader_2.png?600 |Image Loader Variable}}
-  * Execute the workflow
-    * The Versago images table is updated with the needed information and the files are copied to the folder used by Versago.
-    * If an image already exists for a given ID and size, it will be updated.  Otherwise, the new image is added.
-====Register Images Manually====
-Versago images are most commonly imported and registered using a Bizweaver workflow. It is also possible to manage image information manually, as described here.
-===Image Files===
-Four image sizes are required as noted above.  The images should be placed in the older //C:\Program Files(x86)\TWBS\Versago\WebApp\SiteImages//.
-===Image Maintenance Form===
-The **Image Maintenance** form can be used to update information created through the Bizweaver upload process or to add image information manually.
-{{:versago:imagemaintenance.png?600|Image Maintenance}}
-  * //File Name// is the name of the image file without the extension; for example 12345 rather than 12345.png.
-  * //File Size// is the size of the file in **pixels**.  Values will be 45, 65, 250, or 1024.
-  * //File Path// is the abbreviated file path of the image file.  It will always be **\SiteImages\FileName.Ext**.  So using our previous example the entry will by __\SiteImages\12345.png__.
-  * //Intersection ID// is used to match the image file to its associated object.  In the example image below, the image file is associated with item 790824300010.
 <WRAP center round info 80%>
-The file name is typically the same value as its associated object.  So item number images carry the associated item number, Business Partner logos would carry the BP Code, etc.  This association is how the Bizweaver process works, and should also be used when manually entering image information.
+Video regarding images and Data Views
 </WRAP>

Wiki

User Tools

Site Tools

Differences

Page Tools