Baanboard.com

Go Back   Baanboard.com > Forum > Baan Quick Support: Functional & Technical > Tools Development

User login

Frontpage Sponsor

Main

Poll
As a Customer What would do to keep your ERP Implementation intact
Proactively define Business Process-- Take the Project Ownership
50%
Handover everything to System Integrator from drawing BP till implementation of ERP
0%
Hire more inhouse skilled & capable IT Resource to work directly with SI
50%
Rely on SI Architects/Consultants
0%
Total votes: 4

Baanboard at LinkedIn


Reference Content

Reply
 
Thread Tools Display Modes
  #1  
Old 2nd January 2020, 05:53
KiranKrishna KiranKrishna is offline
Junior Member
 
Join Date: Jan 2019
Posts: 11
KiranKrishna is on a distinguished road
Baan: FP2 - DB: My SQL - OS: Windows
Compilation error

Hello,

Getting error when compiling the report of standard session.
"Error: Unresolved reference to function 'function.str.replace_.is.not.supported.with.tiv.lower.than.1700'".

Regards,
Kiran Krishna.
Reply With Quote
Sponsored Links
  #2  
Old 2nd January 2020, 10:47
bdittmar's Avatar
bdittmar bdittmar is offline
Guru
 
Join Date: Apr 2002
Location: Germany, 50.584097,8.544078
Posts: 1,847
bdittmar will become famous soon enough
Baan: 2.2/3.1/4c4/LN6.1 FP6/FP9/HiDox Tools 10.7 - DB: tbase, ms-sql7, oracle10gV1, 11g - OS: HP-UX, W2K3, SLES
Tiv

Quote:
Originally Posted by KiranKrishna View Post
Hello,

Getting error when compiling the report of standard session.
"Error: Unresolved reference to function 'function.str.replace_.is.not.supported.with.tiv.lower.than.1700'".

Regards,
Kiran Krishna.
Hello,
your ToolsInterfaceVersion must be equal or higher than 1700 !

Regards
__________________
//Bernd
Reply With Quote
  #3  
Old 3rd January 2020, 04:51
KiranKrishna KiranKrishna is offline
Junior Member
 
Join Date: Jan 2019
Posts: 11
KiranKrishna is on a distinguished road
Baan: FP2 - DB: My SQL - OS: Windows
Hello Bernd,

yes,but it is a standard session.
is there any other alternative to use str.replace$() in the standard session.

Regards,
Kiran Krishna.
Reply With Quote
  #4  
Old 3rd January 2020, 10:50
bdittmar's Avatar
bdittmar bdittmar is offline
Guru
 
Join Date: Apr 2002
Location: Germany, 50.584097,8.544078
Posts: 1,847
bdittmar will become famous soon enough
Baan: 2.2/3.1/4c4/LN6.1 FP6/FP9/HiDox Tools 10.7 - DB: tbase, ms-sql7, oracle10gV1, 11g - OS: HP-UX, W2K3, SLES
Tiv 1700

Quote:
Originally Posted by KiranKrishna View Post
Hello Bernd,

yes,but it is a standard session.
is there any other alternative to use str.replace$() in the standard session.

Regards,
Kiran Krishna.
Hello,
Code:
TIV 1700
With TIV 1700 the following functionality has been added:

Porting set 8.7a
Added support for namespaces in XML api. 
alloc.mem() supports resizing of any dimension. 
Functions pos() and rpos() support an optional offset argument. 
Enterprise Server 8.7
New string functions added:
str.compare() 
str.containsMBchar() 
str.equals() 
str.endswith() 
str.startswith() 
str.insert$() 
str.remove$() 
str.replace() 
str.replace$() 
str.sizeof() 
str.substring$() 
New path string functions added:
path.change.extension() 
path.combine() 
path.directory() 
path.filename() 
path.filename.without.extension() 
path.extension() 
path.has.extension() 
path.dir.separator() 
path.separator() 
New cURL convenience functions added:
curl.download.data() 
curl.download.file() 
curl.download.stream() 
curl.download.string() 
curl.http.status$() 
curl.upload.data() 
curl.upload.file() 
curl.upload.stream() 
curl.upload.string()
Getting error when compiling the report ..... ?

If your porting set fits, set the TIV of the report to 1700 and compile again.

Regards
__________________
//Bernd

Last edited by bdittmar : 3rd January 2020 at 15:24.
Reply With Quote
  #5  
Old 6th January 2020, 05:43
KiranKrishna KiranKrishna is offline
Junior Member
 
Join Date: Jan 2019
Posts: 11
KiranKrishna is on a distinguished road
Baan: FP2 - DB: My SQL - OS: Windows
Hello,

Getting errors while running the code.
Could you please explain in detail that how to use this script in my code.

Regards,
Kiran.
Reply With Quote
  #6  
Old 6th January 2020, 14:05
OmeLuuk's Avatar
OmeLuuk OmeLuuk is offline
Guru
 
Join Date: Mar 2002
Location: The Netherlands
Posts: 1,131
OmeLuuk is on a distinguished road
Baan: Infor LN 6.1 10.2.1 > 10.7 - DB: MS SQL2008 - OS: VM WindowsServer2008R2
First determine your current Tools Interface Version:
In the Menu Browser choose Help About Infor LN
Click on System Info ...
Session ttsit0100m000 starts, on the General Tab you can see the Tools TIV number (portingset and tools version related) Probably more than 1700

What is your current TIV? (A)

Set your current development package-VRC to the package-VRC of the program script, then doubleclick on the program script line in ttadv2530m000 *edit* on your report script in ttadv3530m000 and locate the Tools Interface Version field, it probably has value 0 or an older (lower) value.

What is the current used TIV? (B)
Enter the TIV from the first (A, probably higher than 1700) field into the second (B).

Compile and your warnings are gone.
__________________
Also read Luke 24:4-8
Reply With Quote
  #7  
Old 6th January 2020, 16:39
KiranKrishna KiranKrishna is offline
Junior Member
 
Join Date: Jan 2019
Posts: 11
KiranKrishna is on a distinguished road
Baan: FP2 - DB: My SQL - OS: Windows
Hello OmeLuuk,
thank you for your response.
My current TIV is 1000, and porting set value is 8.9a with this i unable to use these functions. Now, my requirement with this how can i use this functions in the standard session without changing the TIV number.

Regards,
Kiran.
Reply With Quote
  #8  
Old 8th January 2020, 15:48
OmeLuuk's Avatar
OmeLuuk OmeLuuk is offline
Guru
 
Join Date: Mar 2002
Location: The Netherlands
Posts: 1,131
OmeLuuk is on a distinguished road
Baan: Infor LN 6.1 10.2.1 > 10.7 - DB: MS SQL2008 - OS: VM WindowsServer2008R2
If it is true that your portingset is 8.9a and you say that your TIV is 1000, then I assume this has to be the used TIV (B).

The bshell with Porting set 8.9a has TIV 1900 (with Enterprise Server 10.3)
Your TIV 1000 is the initial TIV level for Porting set 7.5a and application Infor LN without feature packs.

TIV 1700 links to Enterprise Server 8.7 (Infor LN FP7) and Porting set 8.7a.

My guess would be: input 1900 in the report as TIV and you can compile and run your report without errors.
__________________
Also read Luke 24:4-8
Reply With Quote
  #9  
Old 8th January 2020, 18:48
NPRao's Avatar
NPRao NPRao is offline
Guru
 
Join Date: Aug 2001
Location: Pacific NW, USA
Posts: 3,120
NPRao will become famous soon enough
Baan: Baan 4-5,5.2(Reger),LN-6.1,Infor LN-10.x - DB: Oracle,MS-SQL - OS: HPUX, Linux, Windows
Quote:
My current TIV is 1000, and porting set value is 8.9a with this i unable to use these functions. Now, my requirement with this how can i use this functions in the standard session without changing the TIV number.
Kiran,

Who gave the "requirement" to use those functions without changing the TIV number?

The simple answer is NO, it is not possible to override that Tools parameter setting.

Refer to the latest Tools Programmers Manual -
Quote:
Tools Interface Version (TIV)
The Tools Interface Version (TIV) is a concept supported by the Infor Enterprise Server to guarantee backward compatibility. By setting a TIV number to each object the behavior can be different for incompatible features executed with different versions of the Porting set or Infor Enterprise Engine. The TIV number is a property of the program and library scripts, and can be defined in session "Program Scripts / Libraries (ttadv2530m000)". The bshell also has its own TIV number.

Determining TIV number
Developers can determine which TIV number is used in an object or Porting set and may use this information to use a different program flow. Next macros are known to determine a TIV number.

Macro Description
GET.BSHELL.TIV() Returns TIV number of running bshell
GET.TOOLS.TIV() Returns TIV number of tools
GET.OBJECT.TIV() Returns the TIV number of the current object, as specified with the -T option of the compiler when it was compiled.
GET.OBJECT.TIV(string object) Returns the TIV number of the specified object, as specified with the -T option of the compiler when it was compiled.

Caution
When updating a component to a higher TIV level, it can be necessary to do rework. This is for example the case when adopting TIV level 1075 (or higher). Whatever the reason is to do the TIV level upgrading, the rework for Record selection must be done. The session will not function with the old record selection mechanism anymore. Mandatory rework is indicated in the table below.

Supported Porting set TIV numbers
The supported TIV numbers related to Porting set versions are listed below.

TIV Type Description Remarks
200 bshell original TIV level when TIV was introduced in 4c
500 bshell original TIV level when TIV was introduced in Corelli
1000 bshell

tools
Initial TIV level for Porting set 7.5a
1010 bshell Initial TIV level for Porting set 7.6a
1012 bshell

tools
Porting set 7.6a.01 Functions for Outbound Publishing

String size limit removed for xmlSetAttribute and other xml functions

db.get.child.transaction function added in bshell

1014 Tools Added tt.is.domain.separated() function.
1020 tools
Enterprise Server 8.2

1050 bshell Porting set 7.6b Added Unicode support.
1075 bshell

tools
Porting set 7.6c

Enterprise Server 8.3
Note: Mandatory rework in record selection.
1076 bshell Porting set 8.2b
1078 bshell Porting set 8.2b.01
1100 bshell Porting set 8.3a
1101 bshell Porting set 8.2b.01 changed interface handle.report.pool() to handle more than 252 arguments

added syslibpath.env.var$() bshell function. Useful for ERP installer to determine system dependent env. var.

1200 bshell

tools
Porting set 8.3b

Enterprise Server 8.4

1300 bshell

tools
Porting set 8.4b

Enterprise Server 8.4

New functions for handling field dependencies.

1306 tools
New behavior in Enterprise Server 8.4 for ncrs selection groups
1501 tools Function tt.label.desc.by.lang added.
1601 bshell
Porting set 8.6a

1620 bshell
Porting set 8.6a.01

1641 bshell
Porting set 8.6a.02 (rebuild)

Added function mb.coerce.to.sb()

1660 bshell
Porting set 8.6a.03

1700 bshell

tools
Porting set 8.7a

Enterprise Server 8.7
Possible rework needed when moving to object TIV 1700 for use of the alloc.mem() function.
1753 tools
Enterprise Server 8.7a

1800 bshell

tools
Porting set 8.8a

Enterprise Server 8.8

1801 tools
Enterprise Server 8.8

1802 tools
Enterprise Server 8.8

1804 tools
Enterprise Server 8.8

1900 bshell

tools
Porting set 8.9a

Enterprise Server 10.3

2000 tools
Enterprise Server 10.4

2010 bshell
Porting set 9.0a.01.
New cURL functions to support secure email.

New functions to support error bypass

2020 bshell
Porting set 9.0b

2030 bshell

tools
Porting set 9.0b.01

Enterprise Server 10.4.2

2040 tools
Enterprise Server 10.4.2

2050 bshell
Porting set 9.0c.01

2100 bshell

tools
Porting set version 9.1a.

Enterprise Server 10.5

2110 tools
Enterprise Server 10.5.0.1

2120 bshell

tools
Porting set version 9.1b.

Enterprise Server version 10.5.1.

2130 bshell
Porting set version 9.1b.01.

2140 bshell

tools
Porting set version 9.1c.

Enterprise Server version 10.5.2.

2150 bshell

tools
Porting set version 9.1c.01

Enterprise Server version 10.5.2.1
Added TLINK macro

2200 bshell

tools
Porting set version 9.2a.

Enterprise Server version 10.6.

2201 tools
Enterprise Server version 10.6

2202 tools
Enterprise Server version 10.6

2210 bshell

tools
Porting set version 9.2a.01

Enterprise Server version 10.6.0.1

2220 bshell

tools
Porting set version 9.2b

Enterprise Server version 10.6.1

2230 bshell

tools
Porting set version 9.2b.01

Enterprise Server version 10.6.1.1

2300 bshell

tools
Porting set version 9.3a

Enterprise Server version 10.7

2310 bshell

tools
Porting set version 9.3b

Enterprise Server version 10.7.0.1


Base TIV levels per Enterprise Server Feature Pack
The Base TIV levels per Feature Pack are as specified below. Those levels are the base levels. During the lifetime of a Feature Pack, additional numbers may be inserted.

If software is developed on a 'latest Feature Pack' development system, for release to customers who might be on a lower Feature Pack, the TIV level of the software should be maximized to the base level of the target Enterprise Server Feature Pack. If specific functionality within the target Feature Pack is necessary, installation of additional tools solutions or another Porting set might be necessary before the newly developed software works correctly.

Example: when developing software for an ES 7 (Infor LN FP1) system, the TIV level of the new components should be maximized on TIV level 1010. Only when the function tt.is.domain.separated() is used the level should be set to 1014 (And the target system needs to have solution 202854).

Version BASE TIV level
Infor LN without feature packs 1000
Enterprise Server 7 (Infor LN FP1) 1010
Enterprise Server 8.2 (Infor LN FP2) 1020
Enterprise Server 8.3 (Infor LN FP3) 1075
Enterprise Server 8.4 (Infor LN FP4) 1200
Enterprise Server 8.5 (Infor LN FP5) 1500
Enterprise Server 8.6 (Infor LN FP6) 1600
Enterprise Server 8.7 (Infor LN FP7) 1700
Enterprise Server 8.8 (Infor LN FP8) 1800
Enterprise Server 10.3 (Infor LN FP9) 1900
Enterprise Server 10.4 2000
Enterprise Server 10.4.1 2020
Enterprise Server 10.4.2 2040
Enterprise Server 10.5 2100
Enterprise Server 10.5.0.1 2110
Enterprise Server 10.5.1 2120
Enterprise Server 10.5.1.1 2130
Enterprise Server 10.5.2 2140
Enterprise Server 10.5.2.1 2150
Enterprise Server 10.6 2200
Enterprise Server 10.6.0.1 2210
Enterprise Server 10.6.1 2220
Enterprise Server 10.6.1.1 2230
Enterprise Server 10.7 2300
Enterprise Server 10.7.0.1 2310

Note: The TIV level can not be set higher than the current level of the tools or Porting set.
__________________
The art of perfection does not lie in doing extraordinary things but, doing ordinary things extraordinarily well. [-N. Prashanth Rao]
How To Ask Questions The Smart Way,BaaNBoard,NPRao
Reply With Quote
  #10  
Old 9th January 2020, 06:45
KiranKrishna KiranKrishna is offline
Junior Member
 
Join Date: Jan 2019
Posts: 11
KiranKrishna is on a distinguished road
Baan: FP2 - DB: My SQL - OS: Windows
Hai,
Thanks for your information.

I thought there is some alternative to override this issue.
It's okay.

Regards,
Kiran.
Reply With Quote
  #11  
Old 14th January 2020, 12:46
OmeLuuk's Avatar
OmeLuuk OmeLuuk is offline
Guru
 
Join Date: Mar 2002
Location: The Netherlands
Posts: 1,131
OmeLuuk is on a distinguished road
Baan: Infor LN 6.1 10.2.1 > 10.7 - DB: MS SQL2008 - OS: VM WindowsServer2008R2
Quote:
Originally Posted by NPRao View Post
Who gave the "requirement" to use those functions without changing the TIV number?
Well I have to admit, you are more or less right in questioning the question.

When a (standard) report is using these functions, the TIV of the report should have the TIV setting corresponding the functions used. New functions may be added (and other functions deprecated) with a new tools update.

However, since report sources are distributed, it is possible to copy functionality from one report and apply it in another (but without setting the right TIV value for the copy). Then you will get compilation errors and the newly copied code will not work.

After telling the compiler this piece of code is compliant with a certain tools version (by setting the TIV), it will be compiled differently and the functions will work as they should be.

As a rule of thumb it is safe to set the report TIV to the (latest) system wide TIV (set B with value A)

Special cases are intermediate changes in the tools behavior where newer TIV will "break" wanted "fixed" functionality (depending on the perspective). In those cases forcing an older TIV, will "select" a certain behavior. We used this when the record selection changed and also for another query issue.
__________________
Also read Luke 24:4-8
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to create an AFS pralash AFS/DDC/OLE: Function servers 7 11th October 2018 16:13
How to call AFS in sp24? PV Ramone AFS/DDC/OLE: Function servers 4 2nd September 2008 11:06
[Critical] Tape Backup problem. flysurfing Operating Systems & Databases 14 31st August 2007 07:38
DDC and Triton3.1 a1 saso.its AFS/DDC/OLE: Function servers 2 7th January 2004 10:39
Running a Baan script from UNIX command line; ba6.1 runtime options chadwickh Tools Development 18 25th September 2002 22:48


All times are GMT +2. The time now is 14:58.


©2001-2018 - Baanboard.com - Baanforums.com