nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DCR Refresh

SirishaPandu

I have Parent and Child DCR's in different branches

when a Child-DCR is opened in edit mode it fetches values from its corresponding parent and updates the child; accomplished using call server on forminit which reads Parent DCR and writes the values to Child DCR on back-end.

when the child-DCR gets loaded I need to refresh the form manually to see the updated values.

I tried handle refresh in Javascript but it is throwing error saying unable to read/parse dct-file
Tried IWDatacapture.refreshForm();----No Use

Please find the screenshots

Thanks in Advance

Find more posts tagged with

Comments

triple

How about with

IWDatacapture.redraw();

Thanks

SirishaPandu

hey thanks for the response......

function getGenerateStatus(genSuccess) {
if (genSuccess == "SUCCESS"){
IWDatacapture.redraw();
}
}
callback function from perl
no Success !!

triple

Are you using redraw from perl if so

you have to use this

var api = parent.getScriptFrame();

api.IWDatacapture.redraw();

this may helps

Thanks

SirishaPandu


Javascript Code
---------------
IWEventRegistry.addFormHandler("onFormInit", init);

function init()
{
//CALL SERVER TO UPDATE CHILD
var params;
var params = new Object();
var Name = IWDCRInfo.getDCRName();
params.Name=Name;
params.WA=waPath;
IWDatacapture.callServer("http://"+server+"/iw-bin/child_update.ipl", params);

}

function getGenerateStatus(genSuccess) {
if (genSuccess == "SUCCESS"){
 IWDatacapture.refreshForm(window.location.href);

 }
 return;
}


Perl Code:
----------
#!D:\Programs\Interwoven\TeamSite/iw-perl/bin/iwperl
#======================================================================
# This script is called from a DCT via FormAPI
# It's purpose is to update the Child Resx
#======================================================================

use CGI qw(unescape);
use TeamSite::Config;
use AppConfig::File;
use XML::Twig;
use File::Find;
use XML::XPath;
use XML::XPath::XMLParser;
use TeamSite::I18N_utils;
use HTML::Entities;
use Time::HiRes qw(time);
use TeamSite::XMLnode;
use Encode;

use open ':utf8'; # makes sure that any file handles which you open are treated as utf8

binmode (DCR, ":UTF-8"); 
binmode (STDOUT, ":UTF-8"); # these file handles are already open for you - change them to utf8
binmode (STDIN, ":UTF-8");
binmode (STDERR, ":UTF-8");

$|=1;

$cgi = new CGI();

my $iw_home = TeamSite::Config::iwgethome();
my $hostname = TeamSite::Config::hostname();
my $iw_mount = TeamSite::Config::iwgetmount();
$hostname =~ s|(.*).hrbl.net|$1|;

$DEBUG = 1;
$debugfilename = "$iw_home\\tmp\\test\\Resx_Child_Update.log"; 
debug("------RESX CHILD UPDATE LOGGING STARTED------------");

my $genSuccess = "";
my $change_cat = "None";

my $dcr_name=$cgi->param('Name');
my $workarea=$cgi->param('WA');

//Code Here

$genSuccess = "SUCCESS";
if($genSuccess eq "SUCCESS"){
debug("Im Done $genSuccess");
# Pass the result back to the .js
my ${js} .= 'parent.getScriptFrame().getGenerateStatus("' . ${genSuccess} . '" );' . "\n";
print CGI::header(), CGI::start_html( -script => ${js} ), CGI::end_html();
}
sub debug {
return unless $DEBUG;
my ($message, @rest) = @_;
open (DEBUG, ">>$debugfilename") or die "Can't open $debugfilename: $!\n";
print DEBUG "$message\n";
close DEBUG;
}

ISCBorisB

It *seems* that your problem stems from the callServer execution timing. With the loaded DCR Server's callback
modifications should become visible immediately, no redraw or refresh needed.

So... Not sure if that will help but you may want to postpone your Init Function execution till DC Form is fully loaded.
I've illustrated this little hack [post=109242]here[/post].

SirishaPandu

Thanks for the Response

Sorry to say but it didn't work for me.

ISCBorisB

Thanks for the Response

Sorry to say but it didn't work for me.

Oh, well...

There is nothing to be sorry about. I was not sure if that's the problem - and indicated as much.
Your callback logistics and generated JS syntax seems correct. I do not think we can help more without
looking at your Environment or trying to replicate the problem locally.

So, divide and conquer. Place alerts in strategic places and see what you are getting and when you
are getting it, it should provide some clues.

SirishaPandu

Thanks for the reply, I will try