hi,
created internal issues for bug fixes and enhancements. (Issue numbers: 11276, 11277, 11279)
also when you publish the project don't publish it to the bin folder.
publish it to other directories except for your project directory.
because Suite tries to manipulate these files in your out folder.
hi malfaqeeh,
the problem is the output folder of your published files.
remove the project from Suite and then delete the bin & obj folders...
then add your solution again to Suite.
Finally, try generating the entity again
No problem. hope it solves...
we'll respond in 24 hours.
your email rejects.
'mmaldonado@emscltd.com' on 21.07.2022 11:05 552 5.7.0 message content and attachment content guidelines. ku7-20020a170907788700b007052b183d51sm547237ejc.132 - gsmtp
Probably your email provider doesn't accept archive files containing code. We'll share with you a Google Drive link.
Suite doesn't check the version each time opens, so remove the project and add it again to see the version info.
my suggestion would be; create another field called ExternalId. This will be the ID field of your legacy database and you'll use guid/int for your new table. So you can still match your legacy table with this ExternalId.
hi, we send you an email containing the related files
Why do you use string primary key? Using string as the type of primary column is not a good approach because If our values can not be generated sequentially and with an Incremental pattern, this may cause database fragmentation and decrease the database performance.
The reason we put there is, sometimes you might need to migrate from a legacy database and you may want to first populate your new database table from a legacy string ID field table. In this case, you need to either change it to Guid, auto increasing numeric fields or you need to write a logic to create a unique value for each record after the Suite code generation.