• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Data Selection on Versions

graham_jones

Active Member
Hi,

Can someone please put me straight on this one ...

I created a version of a standard JDE report on client 1, changed the data
selection criteria, checked in the version, built and deployed it to the
server. Client 2 runs the report blind and gets the correct data selection.
Client 2 runs the report but opts to change the data selection - still OK.
Now, client 1 checks out the version, changes the data selection and then
checks it back in. When client 2 runs the report blind they still get the
original data selection. Even if I do another server package client 2 still
sees the original data selection. The only way I can get client 2 to see the
new data selection is either by checking the version out or by a client
package.

Am I missing something here?

Regards,

Graham.

B7332 SP13.3 / AS400 (CO on AS400) / Fat clients NT4


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 
G

Guest

Guest
Graham, good question!! I am also a little bit confused with version
handling. In order to get the version to the client I also had to do server
and client update packages. I have also played with the UBE option to submit
SPECS to the server,instead of running the report. I thought this was a way
to get the UBE version to the server without deploying but it does not work.
Can someone please give us some insight?

P.S.. I have been on the list for a few months. I am the CNC support for our
company and have about 6 months overall JDE experience. It is nice to see
that I actually understand some of the e-mail that is sent on the list:))

Crawford Winter
Transamerica Life Canada
 

pwplus

Member
Hello,

I am fairly new to JDE so let me give this a shot.

When client 1 creates the new version and checks it in, the version is made
available to all other clients via the Versions datasource. When a client
gets its list of versions for the report, it gets it from the relational
database every time, i.e. clients do not cache lists of versions.
Consequently, as soon as client 1 checks in the new version, all clients,
including client 2, will see this version in the version list. When a user
on client 2 selects the new version, client 2 checks its local pathcode for
the version selected. Since the new version is not in its local pathcode,
client 2 JITI's it down and runs it. Now that client 2 has the new version
in its local pathcode, it will not JITI it down again. Therefore, any
changes made to the new version by a client other than client 2 AFTER client
2 has run the new version once will not be JITI'ed down to client 2 since
client 2 will check its local pathcode first and find the new version
already there. Once a version has been JITI'ed to a client, the only way to
replace it is to deploy it to the client via an update/full package (good
because JDE will track which clients have the new version via the package
deployment app) or to check it out on the client (bad because JDE will not
track this via the package deployment application).

Regards,
Patrick Plusnick
CANTEX, Inc.
JDE Xe SP14.2, AS/400 ES, NT4 DS, NT4 JAS, 5 Citrix on WIN2000

----- Original Message -

Patrick Plusnick
OneWorld/XE SP 14.2, ES AS/400, DS NT 4, JAS NT 4
 

Adrian_Chimirel

Legendary Poster
You got that right, Patrick!

And, now that the Check-in/out process was understood, let's talk a little about the Enterprise Server ;)
Can IT check-in/out ... anything? No, and THAT is why a server package is needed; to make the Enterprise server that smart, to be able to recognize the modified version.

Good luck,

Adrian Chimirel
Programmer Analyst
LIVE: B732.1 SP12.2, Oracle 806
SANDBOX: XE SP13, 8i
RS/6000, Citrix, 200+ clients
 

DeRay_Scholz

Active Member
Version specs are submitted to the server when you submit your job. If the template specs already exist on the server, you do not need a server package built for a new version.

If you create a new report (R55....), it will not be able to run on the server until you deploy a server package. Once, this has been done you can create new versions of the report all day long which can be run on the server.


DeRay Scholz
The Upper Deck Company
B733.2 sp 11.1 NT 4.0 SQL 7
 

Adrian_Chimirel

Legendary Poster
I beg to differ this one :)
Or, ... let me put it this other way: it is NOT happening EVERYTIME.
This thread started BECAUSE the version's specs did not make it to the Server, therefore OLD data selection was used instead of the new one. Why?

Try this, please:
1-Deploy new template in Portrait orientation.
2-Add only one new version (not all day long) and change its orientation to Landscape.
3-Run it on the server.
4-Ask (me? or) JDE, WHY the orientation @#@$#@!!! DOES NOT CHANGE.
5-Finally, share the answer, please.
6-Regards,

Adrian Chimirel
Programmer Analyst
LIVE: B732.1 SP12.2, Oracle 806
SANDBOX: XE SP13, 8i
RS/6000, Citrix, 200+ clients
 
What you need to do is Submit the Specs to Server. This can be done by
clicking on the version (like you are going to run it) and then click on the
button Advanced. Then click on the check box "Submit Version
Specifications Only". Run the job. This will copy the specs to the server
but will not actually run the job.

This is especially need when you schedule jobs from the server and do not
run them from the JDE menu.

B7332 AS400 Server.
 

CHo

VIP Member
Re: RE: Data Selection on Versions

This functionality is not available in B7321 and B7322.

There is a line in jde.ini called "InstallSpecs=Y" which is suppose to do the same thing, but it doesn't always work especially if the version design has been changed.

What you need to do is Submit the Specs to Server. This can be done by
clicking on the version (like you are going to run it) and then click on the
button Advanced. Then click on the check box "Submit Version
Specifications Only". Run the job. This will copy the specs to the server
but will not actually run the job.

This is especially need when you schedule jobs from the server and do not
run them from the JDE menu.

B7332 AS400 Server.






--------------------------


C Ho

Intermediate Programmer/Analyst
Dundee Realty
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: installing Xe
 

CHo

VIP Member
Re: RE: Data Selection on Versions

Is this functionality in Xe? I have Xe standalone installed, but I can't see this button.

C Ho

Intermediate Programmer/Analyst
Dundee Realty
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: installing Xe
 
Top