I would like to access data from the (in image) highlighted field ID from item table, which exists in a deep nested structure.
I'd then perform various checks if whether the data is initial. In other cases, I'd actually pick data from one of these fields, and input in another field of another table in the deep structure.
What would be the best way to approach this task?
Here is a snippet from what I have to work with:
Declare a table type INPUT-DELIVERY-ITEM. Assign data from ITEM to your table.
Loop the table to access inside rows.
Or just loop the entire INPUT-DELIVERY-ITEM directly.
Related
in a Workshop App, can duplicates (based on some specific columns) be eliminated from an Object Table? And how?
When I see a question like this, it is normally a hint that you may want a more expressive data model. For instance, if each object has a "category" property and you want to make a table of categories with a count of objects in each category you could:
a) Use a pivot table widget on the primary object
b) Create a new "category" object type linked to each object. Then make a regular object table and have a derived property counting the linked objects.
This can add some flexibility, though it has it's own limitations. You'll be able to easily go from categories -> linked objects, but if you have more the 100k objects and try to search around to the linked categories, you'll hit a limitation. So whether this approach works will depend on the semantics and scale of your data model.
I have a PDF file which will contains some data like below structure.
I want to use Azure Form Recognizer to get the data.
How can I set the label with Table.
While tagging with Table, it need to specify the Column and Row.
You must select a table from the Form recognizer tag insertion field. The important thing here is to choose the table type (fixed sized or row dynamic).
Then you must point to the fields in the table by manually creating the columns. If there are no columns, I recommend you to label the fields one by one, or you can create imaginary columns and then delete these imaginary columns by writing a script.
You can find more detailed information at the link below.
Use table tags to train your custom template model
Form Recognizer should extract this table automatically as part of the layout information extract from a document. Did Layout succeed to extract the table ? Do you also want to structure it in a certain structure ? If yes, you can also train a custom model (template) and label the table. Labeling the table can be done in any format. That table you label does not need to be in the same structure. For example You can create a 4 column table form this data with Age, Name, Weight, Hight as the columns or if this is a single row table you can also label it as key value pairs.
Try out the Form Recognizer Generic Document pre-built it might extract these as key value pairs out of the box - https://formrecognizer.appliedai.azure.com/studio/document
Folks:
I have recently begun working with xPages. I have a view of documents that needs to present data from other related documents in six separated columns. What I am trying is to use a Computed column that does a lookup to a view with a concatenated string. My intention was to parse this into the 6 columns of data. It isn't working and it may be silly of me to try referring to a computed column in another computed column.
Another alternative was to have the underlying view present the UNID of the other document and then do a #GetDocField on the xPages view.
So I have two questions:
1) May I programmatically refer to a Computed column in a view from another Computed column?
2) For efficiency, what would be the best way to present data like a 'join' in a view?
I appreciate your attention and help.
Cheers,
John Collis
Can you try to “go native” ? You build one view that contains both documents arranged to be in that view after each other. So you have Type1,Type2,Type1,Type2 etc.
Then use a repeat control to render a table or list “joining” the two rows.
This would save you doing tons of lookups.
Eventually you use that view as Json Rest source to do the joining in Json
I would create a Java bean that returns a list of Java objects that contain your data.
We have a set of BLC/DAC for a customization that has multiple tables with the given relationship
Table1 - T1ID (int-autoincrement), T1CD (char-substitute key)
Table2 - T2ID (int-autoincrement), T2CD (char-subsitute key), T1ID (reference to T1ID)
where the records in Table2 are unique for each given T1ID selected.
The initial design specification was for the users to select first the Table1 value, then the Table2 value (UsrTable1Value, UsrTable2Value respectively) in the data entry screens.
The users have recently asked if it's possible to combine these into one field simular to a Dimension selector so that there is one field resulting in "Table1-Table2" stored as T2ID.
My first thought was to simply create a subclassed dac with a concatenated property for T1CD-T2CD and base the substitute key off that however performance is a problem when that is done (1.6 million records). The delay is in the framwork side as it appears it processes the entire recordset when generating the concatenated substitute key.
Based on that I thought perhaps instead to simply generate a PXDimension configuration for this however I can't find any reference to make Dimension 2 rely on the value of Dimension 1.
I know i could always create a view that does this but i'd prefer to keep it within the framework if possible.
That basically brings me to two questions
1) Outside of a view, is there way to concatenate fields in the BQL so the lifting is done on the SQL and not with a calculated property?
2) Does anyone have or know of a sample of custom Dimensions where the values in level 2 depend on the value in level 1?
Any suggestions would be appreciated.
Out of the box, dimension selectors are designed to work only with Segmented Keys and won't be able to handle values from multiple tables. In theory, it can be possible to populate segment popup from different tables within a custom DimentionSelectorAttribute. However, this will additionally require to store each T1ID/T2ID pair in a separate table with some other column declared as a key (same concept used in the Sub table to store sub accounts: SubID is a key and SubCD stores values composed from multiple segments).
My personal opinion, the effort is just not worth it. Going one step further, I would check with the customer on how they expect navigation buttons (first, prev, next, last) to work with their segmented input control? If following standard Acumatica UI design with separate input created for every key field, no additional effort is needed to properly handle both data entry and navigation.
My view is one application and a required form along with few fields are in different application.
Point one: A View's selection formula does not "select a form". It selects documents. These documents are (usually) created with a Form, and they (usually) contain an item called "Form" which contains the name of the Form that they were created with. So a selection formula SELECT Form = "Foo" means that the view will show all documents with an item named Form that contains the value "Foo".
Point two: A View can only select documents that are in the same database that contains the View. It cannot select documents that exist in another database.
Ergo, there is no possible forumla that selects documents in another database that were created with a given Form.
I'm assuming you probably have some keyword documents in a different database, and you'd like to use a key in the main document to pull some matching information from the keyword database. In other words, you'd like to do a "join" in your Notes view.
You can't do this, never mind whether the documents are in the same database. This is not a relational database.
There are options, however.
You could create a "user definable" column and automatically update the column formula in a profile document so that the formula can calculate the keyword correspondences. You would have a periodic agent look at the keyword database and construct an updated formula such as, #Select("a"; "b"; "c";...; ChoiceNo) to convert the number field ChoiceNo to the value "a" (for 1), "b" (for 2), etc. If you can write a formula to display the correct values for the current keywords, this is workable provided the list never gets too long.
Domino servers are capable of accessing a DB2 relational database to construct a view index, using a feature called DB2NSF. So you can actually do a join -- but your NSF data has to be stored in DB2 as its back-end, rather than beinf stored in the NSF, for this to work. This is probably going to be more work than it's worth to you for this application.
If it is an XPages application, you can create your own data set however you like for feeding to a repeat control.