Hi,
I have exported an Appian Application from server A and Import into server B.
But, when I looked into Server# B after import there in no Application name, but I was able to see individual objects.
Can someone advise, what needs to needs to be done if I have to get the same application name from Server# A to Server# B.
Advise if I have to any other process to bring the code from one server to another server.
Server# A
Server# B
Discussion posts and replies are publicly visible
Is it possible that you don't have permissions on the application object? You need at least viewer permissions on the application to be able to view it in the Appian Designer.
I have full access on the target server (Server #B).
I have observed below issue.
I am trying to export from server# A where I don't have any missing Precedents.
Where as when I try to Import on server# B, I getting messages like below(I am posting one of the message below). Any idea why it is happening like this.
The site [id= uuid=c219ab90-d387-48f0-a0c0-cc2bb5b3e8a3] was not imported because a required precedent is missing: content [uuid=_a-0000e7df-52f7-8000-e595-01ef9001ef90_193651 location=Logo Image] cannot be found. (APNX-1-4070-001) (APNX-1-4071-006)
Can you check to see if the export failed for some objects for any reason? I wonder if the object existed in the package (so it wouldn't be a missing precedent), but for some reason it didn't get exported, so the import failed.
When I look into the Export log, it was showing only 1 problem.
Where as, my Import was showing plenty of errors.
I have also verified both servers versions. Both were showing same version (21.4).
Any other clue for these kind of issues.
Thanks.
Rao2022 said:Where as, my Import was showing plenty of errors
that's what we'd expect - the export log indicates an object was omitted, which, when you try to import the resulting package, will likely result in cascading errors due to that missing object.
Now, I have deleted the Constant which is not being used anywhere. My export is good now.
But, still import showing same list of Problems and Warnings.
Hi
If this is brand new environment and you don't have any inflight instances and no data associated with it delete all the objects from object view and try re-importing the Application again. Some times due to some missing objects the applications may fail to import. Try only this step if you don't have any depended data and you are setting up this environment first time.
That advice makes sense if this is truly a fresh setup. I’ve seen imports fail because of half-created or missing objects left behind from a previous attempt, and clearing everything out before re-importing often fixes it. That said, I’d definitely stress the same warning you mentioned: only do this if there are no in-flight instances and no dependent data. In an environment that’s already been used, deleting objects from Object View can cause more problems than it solves. bitlife