Had tried to setup as below, but from script range(A1).getValues always get
0 (should be 300.0) in debug mode, please help!
=GoogleFINANCE("APL","price")
300.00
Related
I've set up my own node and job according to the documentation - https://docs.chain.link/docs/fulfilling-requests/
Everything works correctly as long as the ORACLE_PAYMENT is set to 1 LINK. I'm expecting a lot of requests and I wouldn't want to buy thousands of LINK, so I would like to lower this fee. I've tried changing it to 0.01 and there was no error but the job doesn't get called unless it's 1.
How can I adjust this fee?
You can modify the fee by using the MINIMUM_CONTRACT_PAYMENT_LINK_JUELS.
Add next line to your job to set fee to 0.01 LINK
minContractPaymentLinkJuels = 10000000000000000
Or add the next line to your .env file to set up it on node globally
MINIMUM_CONTRACT_PAYMENT_LINK_JUELS = 10000000000000000
Finally, double-check that ORACLE_PAYMENT variable in smart contract matches this value.
In my report I am calling the transaction VA01 with BDC data, and everything works as expected, the data is being filled correctly, but bdc_okcode /00 does not work.
I simply add the ok-code to the internal table:
gs_bdcdata-fnam = 'BDC_OKCODE'.
gs_bdcdata-fval = '/00'.
APPEND gs_bdcdata TO gt_bdcdata.
...
CALL TRANSACTION 'VA01' USING gt_bdcdata.
I get a popup that shows the ok code.
My expectation is that it should navigate to the next dynpro.
Also I tried to record the transaction through the transaction SHDB to see if I have to do something differently but the BDC data is basically the same. Playing back the recording shows the same popup with the code.
How can I solve that?
The MODE addition is not used by the CALL TRANSACTION.
If one of the additions MODE or OPTIONS FROM is not used, the effect is the same as if mode had the content "A". Which means the call transaction stops by each screen.
It has to be called like this:
DATA lv_mode TYPE char1 VALUE 'N'. "N - BI won't stop, E - will stop by error, A - will stop at every screen
CALL TRANSACTION 'VA01'
USING gt_bdcdata
MODE lv_mode.
A better option is to use the OPTIONS FROM addition, this gives you more opportunities:
DATA: ls_options TYPE ctu_params.
ls_options-dismode = 'N'. "see explanation above
CALL TRANSACTION 'VA01'
USING gt_bdcdata
OPTIONS FROM ls_options.
I am getting below error in t24 when executing Auth Routine.
FATAL ERROR IN (SENSITIVE ROUTINES CALLED IN LOCAL RTNS
the error appears when the routine gets executed and completed.
i have also tried to call a mainline routine which post OFS,
the problem is the code gets executed successfully, the OFS response is also retured.
but when the routine gets end, it shows this error.
I know some but wanna share everyone this issue was solved, please check below capture
Just add 1 line SENSITIVITY = '' after execute OFS.GLOBUS.MANAGER, all version routine when face this this issue we can do this way no need to create main routine.
I am trying to pass Package variable: packno from Execute SQL Task to Data flow.
Variable is filled with needed value on OnProgress event. The value is:20717.
But on OnPostExecute event this value is cleared and assigned: -1.
So SQL command is executed with -1 value.
Any idea why this is happening?
There is a problem with the server. Everything worked fine on different one.
I'm trying to use the openedge jdbc connector to pull data from an existing progress db but im having column width issues.
As I know already about dBtool option to fix the width. I need to call this dBtool by the 4gl script.
All the input values must be defined in the script.
Is it possible to do? If it is yes, Please provide me a sample script to do this
Here's an example from the official knowledge base (see link below for complete description).
========== PROGRAM LISTING FOLLOWS ==============
FOR EACH _file NO-LOCK WHERE _Tbl-Type = "T":
OUTPUT TO Value("input.txt").
/* SQL Width Scan wFix Option. */
PUT UNFORMATTED "9~n2~n1~n20~n" + STRING (_file-number) + "~n0".
OUTPUT CLOSE.
OS-COMMAND SILENT VALUE ("dbtool Sports2000 < input.txt").
OS-RENAME VALUE ("dbtool.out") value ("dbtool_" + _file-name).
END.
========= example of the input file created by the above script =======
9
2
1
20
20
0
========= example output for a single table ===========
Total records read: 0
SQLWidth errors found: 0, Date errors found: 0
SQLWidth errors fixed: 0
See complete example and better description in the Progress Knowledgebase