Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Hi All,

We have been working on creating tables for the Continuous Database, and in the main we have everything working as we need it.

One major issue for us is that the parter tables no longer appear in the Windows Admin Client Importer, and we use this a lot for allowing cutomers to import bulk data.

Do we have any idea when this issue will be resolved?

Many thanks,

Trevor

RE: Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Tony,

Thanks for your reply:

Hi Trevor,

When you use the code generator to generate a dictionary step from the physical table, does it contain the appropriate table Import settings? Can you provide the generated code from the tool?

Please see below the code generated from the tool:

 

namespace eSuite.Tables
{
[Dictionary("PartnerTables.eentityfield", 1, ReleaseState.Released)]
public class eentityfieldStep : DictionaryStep
{
public override void Structure()
{
CreateTable("eentityfield", "")
.Legacy.SetTableNames("eentityfield", "Eentityfield")
.TableProperties.CodeGeneration(MDOFlags.None, HDBFlags.MergeUpdatesRelations, UdefFlags.None, SentryFlags.None)
.TableProperties.Replication(ReplicationFlags.Down | ReplicationFlags.Up | ReplicationFlags.Prototype)

// Field specifications

// explicit primary key specification needed due to non-default values
.Legacy.PrimaryKey("eentityfield_id", "")
.Legacy.SetFieldNames("eentityfield_id", "EentityfieldId")
.Legacy.SetFieldNames("eentityfield_id", "EentityfieldId")

.AddString("applicationname", "", 50, index: true)

.AddString("entitytype", "", 50, index: true)

.AddString("entity1", "", 50, index: true)

.AddString("entity2", "", 50)

.AddString("entity3", "", 50)

.AddString("entity4", "", 50)

.AddString("entity5", "", 50)

.AddString("fieldname", "", 50)

.AddString("fieldvalue", "", 1024)

.AddDateTime("registered", "", isUTC: true)

.AddForeignKey("registered_associate_id", "", "associate", index: true)
.Legacy.SetFieldNames("registered_associate_id", "RegisteredAssociateId")

.AddDateTime("updated", "", isUTC: true)

.AddForeignKey("updated_associate_id", "", "associate", index: true)
.Legacy.SetFieldNames("updated_associate_id", "UpdatedAssociateId")

;
}


///// <summary>
///// Return the hard-coded list of standard IMP files for a new 8.0 installation;
///// but also populate the travelcurrent record. See remarks!
///// </summary>
///// <returns></returns>
//public override List<string> ImpFileNames()
//{
//// these are the .IMP files used in a traditional INIT + REGISTER
//return new List<string>
//{
// @"I_eentityfield.imp",
//};
//}

///// <summary>
///// Using SQL or other means to prime the table.
///// </summary>
//public override void CustomPriming()
//{
//}
}
}

 

Please let me know if you need any of the other source code.

Cheers

Rich

 

Av: Rich Hacker 19. dec 2017

RE: Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Hi Rich! 

You swiped my deleted post! Arg! OK, lets do this... 

The reason I deleted it was because I had made some [obvious] assumptions that proved wrong. The bottom line is that, as of this writing, Continuous Database does not support Import annotations that would allow third party tables to appear in the Windows client Import screens. By the way, the web client Import capabilities are all hardcoded and not extensible at all... All fields are hardcoded Contact, Person and Product fields.

All custom table Import cababilities have been removed in SuperOffice 8.1/8.2. 

I am interested in learning how big of an impact will this be for partners.

So, how big of an impact will this be for partners?

Av: Tony Yates 20. dec 2017

RE: Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Hi Tony,

Happy new year.  I hope you had a good Christmas.  This would be a pretty significant issue for us as we often import data into our tables, and the importer tool is the easiest way to do this.

With regards to asking if other partners would require this, what is the best way of communicating this question to the partners, as it does not appear that as of yet many partners are using this particular forum, so would probably not see this post.

Many thanks,

Trevor

Av: Trevor Sharp 4. jan 2018

RE: Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Hi Trevor,

As someone who dislikes having my cheese moved, I share your frustration and grievance. 

Unfortunately the functionality is not likely to be revived anytime soon, regardless how many partners it affects.

My only guidance is to get comfortable with writing new routines to import data into your custom tables.

I do apologize.

Av: Tony Yates 5. jan 2018

RE: Partner Tables created for Continuous Database do not appear in the Windows Admin Client Importer

Ok thanks Tony. :-(

Av: Trevor Sharp 5. jan 2018