Hi everyone, 👋 From the AI Builder product group we want to hear from you.
👉Have you tried Text Generation in AI Builder already? How are you using it? For what use case? Is there anything you would like to see added or changed to make it even better?
👉We are interested in knowing about your AI Builder experience. Please share your story!
Thank you!
@Ashbhatia This new required step should really be a warning and not error. Some workflow simply will not work if a approval step is required after text generation. Please reconsider this new measure as its hindering development work.
I've now encountered an error many times with a specific prompt for a 4 page document. For some reason the Create text with GPT action returns a BadRequest 400 error & the error message says it timed out. It doesn't make sense considering I've had this work on 10+ page documents with many more characters. I wonder if there is something about a set of characters or something in this prompt that causes the time-out or maybe it has many more lines that GPT suspects may be relevant & so it takes it much longer?
Prompt:
From the OCR captured packing list document text provided between [Start of text] & [End of text] markers, extract data for each of the example JSON fields between [Start example JSON] & [End example JSON].
Be aware, OCR text may contain errors like wrong characters or missing formatting.
In the JSON output, replace [data] with each field's extracted data text using only string datatypes. Use a string value of "NULL" when the field's data text is not found in the document text provided.
Convert all numbers to a standard 2-place decimal notation.
Convert all dates to international format "yyyy-mm-dd". For example, dates in the document text may start as something like 18.05.2024 or 3/21/2025, and need to be converted to 2024-05-18 & 2025-03-21 respectively.
If the document text has more than one Packing List Reference Number, then give a pipe | separated list of each number for the Packing List Reference Number field value like "12345678|98765432".
Packing List Date may also relate to the file's issued date. If there is more than one Packing List Date, then give the oldest, lowest date found for the Packing List Date.
Purchase Order (PO) Number is 2 letters & 8 digits like "PO########". Use only 2 letters, 8 digits for the PO field value.
If the document text includes text from multiple Packing List files then it may contain more than one Consignee Address & more than one Delivery Or Ship To Address. If more than one Consignee Address is found in the document text then give a space pipe space " | " separated list of each address for the Consignee Address field value. If more than one Delivery Or Ship To Address is found in the document text then give a space pipe space " | " separated list of each address for the Delivery Or Ship To Address field value. A hypothetical example of this list structure with more than one address value: "123 St. Miami, Fl 55555 USA | 456 St. Miami, Fl 44444 USA".
The Chemonics Address in the document text often starts with 1275 New Jersey. If such an address starting with 1275 New Jersey is not found, just return "NULL".
Mode Of Shipment (MOS) may also go by Mode Of Transport & the value is usually Air, Sea, or Land.
There may be any number of Product Lines. Each Product Line should include Product Name, Quantity, Unit Price, Line Amount Or Total, Manufactuer, Batch Or Lot Number, Product Manufacture Date (MFG), & Product Expiration Date.
[Start example JSON]
{
"Packing List Date": [data],
"Packing List Reference Number": [data],
"Invoice Number": [data],
"Purchase Order (PO) Number": [data],
"Consignee Address": [data],
"Delivery Or Ship To Address": [data],
"Chemonics Address": [data],
"Mode Of Shipment": [data],
"Final Destination Or Final Delivery Location": [data],
"Special Temperature Requirements": [data],
"Product Lines": [
{
"Product Name": [data],
"Product Quantity": [data],
"Product Unit Price": [data],
"Product Line Total or Amount": [data],
"Manufacturer": [data],
"Batch Or Lot Number": [data],
"Manufacture Date (MFG)": [data],
"Expiration Date": [data]
},
{
"Product Name": [data],
"Product Quantity": [data],
"Product Unit Price": [data],
"Product Line Total or Amount": [data],
"Manufacturer": [data],
"Batch Or Lot Number": [data],
"Manufacture Date (MFG)": [data],
"Expiration Date": [data]
}
]
}
[End example JSON]
[Start of text]
______________________________________________________________________________________________________________________________________________________________
Job......: QPADEV003R Packing list and certificate of weight for 197 xxxxxxxx Date.....: 2022/10/14
Program..: PKDE624R Tour : EATG3 Expected Ship Date 2022/10/14 Time.....: 9:21:39
User.....: MORENCX3 ______________________________________________________________________________________________________________________________________________________________ Page.....: 0001
ListNo Size Gross Width Volume
______ Description ___________________ _____ Qty ___ _________ Wgh Net _________ Wgh Length ______ ______ Height ______ ______
Customer No: 106 0056725901 Dly-Slip3923441 CUST.REF .: PO10022355 PO10022355
1 CASE FROM 11 60,0 cm 50,0 cm 59,5 cm 178500,00
24,954 kg 6,512 kg ccm
2G3170 RT HIV-1 CAL 00001 10
2G3170 RT HIV-1 CAL 00001 4
2G3180 RT HIV-1 CTL 00001 8
2 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
3 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
4 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
5 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
6 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
7 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
8 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
9 CASE FROM 11 60,0 cm 50,0 cm 59,5 cm 178500,00
24,954 kg 6,512 kg ccm
2G3180 RT HIV-1 CTL 00001 22
10 CASE FROM 11 24,954 kg 6,512 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3180 RT HIV-1 CTL 00001 22
11 CASE FROM 11 7,452 kg 0,296 kg 30,0 cm 33,0 cm 37,5 cm 37125,00 ccm
2G3180 RT HIV-1 CTL 00001 1
Customer No: 106 0056725901 Dly-Slip3923442 CUST.REF .: PO10022355 PO10022355
1 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
2 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
3 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
4 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
5 CASE FROM 79 60,0 cm 50,0 cm 59,5 cm 178500,00
24,805 kg 6,363 kg ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
6 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
7 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
8 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
9 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
10 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
11 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
12 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
______________________________________________________________________________________________________________________________________________________________
Job......: QPADEV003R Packing list and certificate of weight for 197 TANZANIA Date.....: 2022/10/14
Program..: PKDE624R Tour : EATG3 Expected Ship Date 2022/10/14 Time.....: 9:21:39
User.....: MORENCX3 ______________________________________________________________________________________________________________________________________________________________ Page.....: 0002
ListNo Size Gross Width Volume
______ Description ___________________ _____ ___ Qty _________ Wgh Net _________ Wgh ______ Length ______ ______ Height ______
Customer No: 106 0056725901 Dly-Slip3923442 CUST.REF .: PO10022355 PO10022355
13 CASE FROM 79 60,0 cm 50,0 cm 59,5 cm 178500,00
24,805 kg 6,363 kg ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
14 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
15 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
16 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
17 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
18 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
19 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
20 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
21 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
22 CASE FROM 79 60,0 cm 50,0 cm 59,5 cm 178500,00
24,805 kg 6,363 kg ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
23 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
24 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
25 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
26 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
27 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
28 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 18
2G3110 RT HIV-1 AMP KIT 96T 00096 3
29 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
30 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
31 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
32 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
33 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
34 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
35 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
36 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
37 CASE FROM 79
24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
38 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
______________________________________________________________________________________________________________________________________________________________
Job......: QPADEV003R Packing list and certificate of weight for 197 TANZANIA Date.....: 2022/10/14
Program..: PKDE624R Tour : EATG3 Expected Ship Date 2022/10/14 Time.....: 9:21:39
User.....: MORENCX3 ______________________________________________________________________________________________________________________________________________________________ Page.....: 0003
ListNo Size Gross Width Volume
______ Description ___________________ _____ ___ Qty _________ Wgh Net _________ Wgh ______ Length ______ ______ Height ______
Customer No: 106 0056725901 Dly-Slip3923442 CUST.REF .: PO10022355 PO10022355
2G3110 RT HIV-1 AMP KIT 96T 00096 21
39 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
40 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
41 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
42 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
43 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
44 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
45 CASE FROM 79
24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
46 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
47 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
48 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
49 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
50 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
51 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
52 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
53 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
54 CASE FROM 79
24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
55 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
56 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
57 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
58 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
59 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
60 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
61 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
62 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
63 CASE FROM 79
24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
64 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
______________________________________________________________________________________________________________________________________________________________
Job......: QPADEV003R Packing list and certificate of weight for 197 TANZANIA Date.....: 2022/10/14
Program..: PKDE624R Tour : EATG3 Expected Ship Date Expected Ship Date 2022/10/14 Time.....: 9:21:39
User.....: MORENCX3 ______________________________________________________________________________________________________________________________________________________________ Page.....: 0004
Gross
ListNo______ Description ___________________ Size_____ Qty___ _________ Wgh Net _________ Wgh Length______ Width______ Height______ Volume______
Customer No: Customer No: 106 0056725901 0056725901 Dly-Slip: Dly-Slip: 3923442 3923442 CUST.REF.: CUST.REF.: PO10022355 PO10022355
2G3110 RT HIV-1 AMP KIT 96T 00096 21
65 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
66 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
67 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
68 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
69 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
70 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
71 CASE FROM 79
24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
72 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
73 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
74 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
75 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
76 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
77 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
78 CASE FROM 79 24,805 kg 6,363 kg 60,0 cm 50,0 cm 59,5 cm 178500,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 21
79 CASE FROM 79 22,051 kg 5,454 kg 60,0 cm 50,0 cm 53,0 cm 159000,00 ccm
2G3110 RT HIV-1 AMP KIT 96T 00096 18
Registration Number: TAN 19 MDR 0584
xxxxxxxxx
Max-Planck-Ring 2
xxxxxxxxxxxxxx
xxxxxxx
[End of text]
Return only the final JSON object. Do not return any other output descriptions or explanations, only the JSON object.
I've created a way to error-handle this by setting a parallel branch to run the GPT action with only the 1st 5000 document text characters & that works to extract all the available data on the 1st page or so. But I'm wondering if there is anything else that can be done on Microsoft's side to improve the model performance & reduce the timeout error.
Looks like we both work with logistics, shipping. I will bookmark this prompt to test with my packing lists later 😁
Has Microsoft started applying AI Credits Usage per Create text with GPT prompt or tokens?
I just had a flow fail due to running out of credits. Now I have many more credits available to apply to the environment, but I wouldn't have expected this to happen with the amount of credits already assigned unless the credit cost/usage for this action was outrageously higher than the $.003 per 1000 tokens listed on Logic Apps.
We are facing the exact same issue here, but thought the problem was on our end since we just created a new Environment specific for AI Builder. I wonder what's happening now because we have a lot of credits. My Power Platform admin was going to reach out to Microsoft
Yes, looks like the action is now taking credits. And oohhhh boy, it is 8.5X MORE EXPENSIVE than the same resources one could access through Azure LLMs or through even the OpenAI HTTP calls. Why does Microsoft think people will pay $.0255 per 1000 tokens for something they could directly call on their own for $.003 per 1000 tokens???
361 Credits for a 28,400 character prompt, using $500 add-on for 1 million credits pricing makes 361 credits = $.1805
Price comparison to Azure which is equivalent with OpenAI pricing.
Why does Microsoft ham-string themselves with stupid pricing every time for Power Platform stuff? They say it is because these are on "low-code" tools with lower skill requirements, but frankly it is the same level of skill as any other system. The way they try to get everyone on this is by not offering things like Power Apps actions in Logic Apps.
@ARB_wcc
At these prices, if anyone is considering using GPT in their Power Automate workflows & you aren’t working with really sensitive data, then you may want to sign up for OpenAI’s direct API services prepare your flows to use the HTTP action to call OpenAI directly.
https://openai.com/blog/openai-api
For my personal projects, I've been using OpenAI's API service almost since its inception. The flexibility and fewer restrictions make it feel like I can accomplish more with OpenAI. However, at my workplace, the OpenAI connector is unfortunately blocked due to DLP policies.
@ARB_wcc
Well next I'm going to test the Azure OpenAI set-up. Because usually in situations like these we can also just do an HTTP request back to an Azure Logic app that uses the Azure version of a service, then send the results in a response back to the flow which can then return it to a Power App or whatever other service that is only available in the regular Power Automate flows. That allows us to get that lower Azure price, even in a Power App.
@ARB_wcc
From what I'm looking at in a test Azure resource & this helpful guide, it looks like one can just directly call an API endpoint for one's LLM set-up & get the response back in the HTTP action. So at least that means no Logic Apps work-around as long as one has all the required licensing for premium connectors.
A practical look at using and building on Azure OpenAI, specifically the "ChatGPT-style" feature (ju...
In an ideal scenario, the process of extracting data from text should be as straightforward and user-friendly as possible, that's why the "preview" connector "Create Text with GPT" became so popular in my opinion. The need for premium connectors or alternative solutions like Logic Apps should be minimized, but as Microsoft continues to evolve its pricing and restrictions for AI Builder, it's becoming increasingly apparent that complex setups may become the standard approach, rather than an exception. This shift could potentially create barriers for users who are looking for simple, cost-effective solutions. By the way, what's insteresting is that this page AI Builder licensing and credit management | Microsoft Learn states that "AI Builder features that are in preview release status are free to use. You don't need to obtain a license to use AI Builder preview features", however, in practice, it doesn't seem like anything is truly free 🤔
Hello,
An engineering issue in our environment monitoring pipeline has caused the “Create text with GPT” action to trigger incorrect credit consumption. Since the “Create text with GPT” action is still in preview, it should not be triggering credit consumption. A fix is in progress and will be rolling out as soon as possible.
We will be proactively reaching out to impacted customers to reimburse the credits that were consumed erroneously. If you believe you have been incorrectly charged for use of the GPT action, please contact: aihelpen@microsoft.com
Additionally, the prices discussed in this forum don’t reflect the definite rates that will be applied. Stay tuned for details on definitive rates that will be announced next month.
We apologize for the inconvenience.
Antoine2F
Well, that explains a lot!
@takolota it looks like you won't have to resort to plan B and plan C 😅
We may have spoken too soon. The original Create text with GPT action is now deprecated and the new Create text with GPT using a prompt action seems more limited because it requires choosing specific prompts & the extraction prompt is more limited.
ALSO I now do not have access to the intricate prompts I created in the original actions as they no longer open.
Thankfully I still have a little time to go back through past flow runs & pull the prompt text from those, but what is Microsoft doing?
They need to fix this asap, I think the post below is the best place to post our complaints now 😅
GPT Prompt Builder goes GA and expands to EU,UK,AU - Power Platform Community (microsoft.com)
@ARB_wcc
I'm looking through this again this morning & it looks like something fell between the cracks with both the new AI Builder GPT action & the classic designer that my flows were still in. On the classic designer, the option to create a new custom prompt isn't clear. I'm testing to see how the custom prompt will work and if it is any extra trouble for users while importing a template flow.
Alright, now there is an issue with custom prompts & solution imports/exports...
So we can no longer export flows as zip folders, we must export flows inside Solution packages. But if your flow uses any custom prompt, then the Solution package will fail to import to any other environment because the environment does not have the custom prompt resource anywhere. 🙄
I could normally use the legacy flow zip import/export or put everything inside a scope to copy to clipboard & paste, but both of those options were removed with the introduction of the new flow designer interface.
It seems the rush to release software has become a race against the calendar, not bugs. It's like Microsoft's playing speed chess with updates—checkmate by New Year's Eve, ready or not.
Maybe they should take a leaf out of Rockstar Games' playbook: good things come to those who wait... a decade if necessary. We'll wait for the win, as long as the final level isn't glitched! 😅
When will solutions support importing packages with custom prompts?
Currently Microsoft has a couple of my projects in a bad catch-22 situation where I can't edit the prompts of the previous GPT preview action because it is deprecated, but I also can't switch to the new GPT prompt action without losing the ability to export & import solutions to different Dev & Production environments.
Hi Takola,
If you copy your prompt created with the Public Preview Create text with GPT and then create a new custom prompt using the former prompt, you should be able to add it to a solution and move it across environments.
Are you saying that this is not working?
We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience! Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up? Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen. Don't miss your moment--start submitting in the Copilot Cookbook Gallery today! Thank you, Engagement Team
We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps. Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!
You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun. Now that you are a member, you can enjoy the following resources: Welcome to the Community News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate. Be sure to subscribe to this board and not miss an announcement. Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows. You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook. Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today. Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome. Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together. Power Automate Community Team
Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp
It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community. As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn! Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report. Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone. Thank you for helping us keep the community clean and useful!